git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: Git List <git@vger.kernel.org>,
	Felipe Contreras <felipe.contreras@gmail.com>,
	Junio C Hamano <gitster@pobox.com>
Subject: Re: [QUERY] Why do we have git-completion.zsh?
Date: Sat, 20 Apr 2013 11:53:29 -0700	[thread overview]
Message-ID: <20130420185329.GB8586@elie.Belkin> (raw)
In-Reply-To: <20130420184539.GA8586@elie.Belkin>

Jonathan Nieder wrote:
> Ramkumar Ramachandra wrote:

>>                             However, I don't understand why we
>> maintain it, because there's a comprehensive first-class completer in
>> ZSH core [1] which I use all the time.  Shouldn't the completion folks
>> be contributing to this instead?
>
> Only if they want to.
[...]
> http://thread.gmane.org/gmane.comp.version-control.git/210022/focus=210024

Sorry, wrong link.  Here's a better one:

http://www.zsh.org/mla/workers/2011/msg00497.html

More fundamentally, your question seems to assume some kind of shared
plan regarding what people work on, rather than each person choosing
to work on what they consider valuable without having to justify it to
others.  I am very happy with Felipe's work on git's completion code
and don't think it does any harm to efforts elsewhere.

Thanks for your interest,
Jonathan

  reply	other threads:[~2013-04-20 18:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-20  9:39 [QUERY] Why do we have git-completion.zsh? Ramkumar Ramachandra
2013-04-20 18:45 ` Jonathan Nieder
2013-04-20 18:53   ` Jonathan Nieder [this message]
2013-04-20 22:39     ` Felipe Contreras
2013-04-21  1:21       ` Felipe Contreras
2013-04-21  4:36       ` Ramkumar Ramachandra
2013-04-21  6:21         ` Felipe Contreras
2013-04-21  6:56           ` Ramkumar Ramachandra

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=20130420185329.GB8586@elie.Belkin \
    --to=jrnieder@gmail.com \
    --cc=artagnon@gmail.com \
    --cc=felipe.contreras@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /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. 
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).