zsh-users
 help / color / mirror / code / Atom feed
From: Simon Ruderich <simon@ruderich.org>
To: zsh-users@zsh.org
Subject: Re: Git completion - contributing to git.git
Date: Sun, 4 Jul 2010 11:58:31 +0200	[thread overview]
Message-ID: <20100704095831.GA14152@ruderich.org> (raw)
In-Reply-To: <87hbkf1vqe.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2445 bytes --]

On Sun, Jul 04, 2010 at 10:45:13AM +0200, Štěpán Němec wrote:
>>> I’d rather not, to be honest.  It’s always a pain to have two files,
>>> as they can become out of sync when patches are sent to one repository
>>> and not the other, users don’t know which version to use, and so on.
>>
>> +1
>>
>> There's nothing special about Git either.  What of the other 500 odd
>> completion functions and 'associated' projects?
>
> What's special about Git is that new options are added and various
> tweaks done _very_ often. The Zsh Git completion, apart from being
> buggy/unfinished (some of the problems were fixed recently), is also
> out of sync, because nobody really follows Git development and updates
> it accordingly.

I'm not very actively following Git's development (always running
latest release though), but I don't think that's the case for the
"normal" user. I consider myself an intermediate/advanced git
user and use _git from the current zsh CVS checkout and I've
never felt _git was missing something important (sometimes file
completion could be even smarter - and maybe faster, but it's
already very good). Sometimes one option or another is missing,
but I don't think that's a big problem as I can just add it (or
ignore it, as I don't need all of git's options anyway).

Thanks by the way for the great work the developers of _git have
done.

> [snip]
>
> The only problem I see is whether there are really enough Zsh users
> following Git development and at the same time able and willing to
> maintain the completion script.

I don't see the difference between maintaining the _git file in
zsh's CVS or in git's git repository regarding the speed of
development of _git.

If an active git developer (or anybody else) wants to update it
in zsh's CVS he only needs to send the patches here and they are
applied quickly.

The only difference is, as others have already mentioned, that
maintaining a file in two places is a very bad thing. And as user
I have to look in many different places (and I even have to know
that the completion exists) to get my completion functions.
That's not a very good idea.

> Štěpán

IMHO moving _git to git's repository only increase the work in
maintaining it, sometimes which could be spend much better in
improving it.

Simon
-- 
+ privacy is necessary
+ using gnupg http://gnupg.org
+ public key id: 0x92FEFDB7E44C32F9

[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]

  reply	other threads:[~2010-07-04 10:03 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 [this message]
     [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

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=20100704095831.GA14152@ruderich.org \
    --to=simon@ruderich.org \
    --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).