From: Junio C Hamano <junkio@cox.net>
To: Shawn Pearce <spearce@spearce.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Contributed bash completion support for core Git tools.
Date: Sun, 17 Sep 2006 18:03:49 -0700 [thread overview]
Message-ID: <7vodtex9xm.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: 20060918004831.GA19851@spearce.org
Shawn Pearce <spearce@spearce.org> writes:
> Since these are completion routines only for tools shipped with
> core Git and since bash is a popular shell on many of the native
> core Git platforms (Linux, Mac OS X, Solaris, BSD) including these
> routines as part of the stock package would probably be convienent
> for many users.
>
> Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
>
> contrib/bash-git-completion.sh | 330 +++++++++++++++...
> 1 files changed, 330 insertions(+), 0 deletions(-)
Hmph. I tried this and found that I like "git pull ."
completion quite a bit. Having said that:
* If many people like it (like me), this may deserve to be
outside contrib/
* Otherwise, it would probably be better to place it in either
contrib/bash/git-completion.sh (with potentially other
bash-related things not just completion, but I do not know
offhand what other kind of hooks would be useful) or
contrib/completion/git-completion.bash (possibly with
completion for other shells).
next prev parent reply other threads:[~2006-09-18 1:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-18 0:48 [PATCH] Contributed bash completion support for core Git tools Shawn Pearce
2006-09-18 1:03 ` Junio C Hamano [this message]
2006-09-18 1:18 ` Shawn Pearce
2006-09-28 16:16 ` Junio C Hamano
2006-09-28 16:28 ` Shawn Pearce
2006-09-18 8:17 ` Johannes Schindelin
2006-09-18 17:29 ` Shawn Pearce
2006-09-18 8:23 ` Junio C Hamano
2006-09-18 17:42 ` Shawn Pearce
2006-09-18 8:31 ` Sebastian Harl
2006-09-18 17:55 ` Shawn Pearce
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=7vodtex9xm.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.