zsh-users
 help / color / mirror / code / Atom feed
From: Frank Terbeck <ft@bewatermyfriend.org>
To: Nicolas Sebrecht <nicolas.s-dev@laposte.net>
Cc: zsh-users@zsh.org, Clint Adams <clint@users.sourceforge.net>,
	 Doug Kearns <dkearns@users.sourceforge.net>,
	 Peter Stephenson <pws@users.sourceforge.net>,
	Nikolai Weibull <now@bitwi.se>
Subject: Re: Git completion - contributing to git.git
Date: Thu, 01 Jul 2010 10:19:14 +0200	[thread overview]
Message-ID: <877hlffwcd.fsf@ft.bewatermyfriend.org> (raw)
In-Reply-To: <20100701010506.GC13062@vidovic> (Nicolas Sebrecht's message of "Thu, 1 Jul 2010 03:05:06 +0200")

Nicolas Sebrecht wrote:
> As a user of Git, I'd like to have Git completion in sync with the Git
> project itself rather than with zsh. I don't update zsh as much as Git.

It's actually fairly trivial to update a single completion without
updating the main shell:
  <http://zshwiki.org/home/config/functions>

> I'm not saying that having completion in the zsh project doesn't make
> sense but that it's more relevant to have latest version of the
> completion in the Git project.
>
> What about starting contributing to Git ('contrib/completion' looks like
> a good path) ?  Could Git completion contributors send their patches to
> the Git project too ?

IMHO it doesn't matter so much *where* a completion is maintained. It's
much more important that it is maintained and updated at all. It would
be great to see more people contributing to `_git'; because frankly,
it's huge and needs more man power. It'd be great to see more people
trying to get it in sync with git's master branch. Personally I'm only
touching it if there's a serious itch I feel, that needs relief. But
most of the time, the completion just works fine for me.

And FWIW, I like it that the zsh repository is the central source of
completion functions. No searching for where to get a completion; no
thinking about which version is right.

Also, maintaining something in two places is a pain in the ass. :)

> PS: I know the Git mailing list doesn't need subscription to post.  Does
> the zsh lists ask for subscribing ?

I don't think you need to be subscribed here either.

Regards, Frank

-- 
In protocol design, perfection has been reached not when there is
nothing left to add, but when there is nothing left to take away.
                                                  -- RFC 1925


      parent reply	other threads:[~2010-07-01  8:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-01  1:05 Nicolas Sebrecht
2010-07-01  8:00 ` Nikolai Weibull
2010-07-01  8:13   ` Richard Hartmann
2010-07-01  8:18     ` Nikolai Weibull
2010-07-01  8:33   ` Nicolas Sebrecht
2010-07-01  9:15     ` Nikolai Weibull
2010-07-01  9:32       ` Frank Terbeck
2010-07-01  9:35     ` Richard Hartmann
2010-07-04  5:50   ` Doug Kearns
     [not found]   ` <AANLkTin9y2_EtnBDYfdG1ctEHP3GkiStbXFMvf3GX3gp__29002.7882242159$1278224383$gmane$org@mail.gmail.com>
2010-07-04  8:45     ` Štěpán Němec
2010-07-04  9:58       ` Simon Ruderich
     [not found]       ` <20100704095831.GA14152__37531.721746973$1278237962$gmane$org@ruderich.org>
2010-07-04 12:09         ` Štěpán Němec
2010-07-01  8:19 ` Frank Terbeck [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=877hlffwcd.fsf@ft.bewatermyfriend.org \
    --to=ft@bewatermyfriend.org \
    --cc=clint@users.sourceforge.net \
    --cc=dkearns@users.sourceforge.net \
    --cc=nicolas.s-dev@laposte.net \
    --cc=now@bitwi.se \
    --cc=pws@users.sourceforge.net \
    --cc=zsh-users@zsh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).