From: "Shawn O. Pearce" <spearce@spearce.org>
To: Ted Pavlic <ted@tedpavlic.com>
Cc: git <git@vger.kernel.org>, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH 2/3] Makes the bash completion script try *bash* completions before simple, filetype completions when a git completion is not found. If bash, completions aren't available, the default file completions are used. This, behavior was inspired by Mercurial's bash completion script.
Date: Tue, 13 Jan 2009 08:38:16 -0800 [thread overview]
Message-ID: <20090113163816.GR10179@spearce.org> (raw)
In-Reply-To: <496CBCED.80402@tedpavlic.com>
Ted Pavlic <ted@tedpavlic.com> wrote:
>
> Second in a series of patches that make bash completions more robust to
> different interactive shell configurations and editors.
>
>
> [PATCH 2/3] Makes the bash completion script try *bash* completions
> before simple
> filetype completions when a git completion is not found. If bash
> completions aren't available, the default file completions are used. This
> behavior was inspired by Mercurial's bash completion script.
Again, I would have used this as my commit message:
bash-completion: Try bash completions before file completions
Try bash completions before any simple file completions
whenever a git completion is not found. This may help
users to complete BLAH BLAH BLAH WHAT THE HECK IS THIS GOOD
FOR ANYWAY.
Behavior was inspired by Mercurial's bash completion script.
No ack, because I still don't understand why this is a good thing.
Yes, I could look it up online in the bash docs. I shouldn't need
to go do research like that to understand the justification for
a change, it should be better explained in the message.
--
Shawn.
prev parent reply other threads:[~2009-01-13 16:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-13 16:10 [PATCH 2/3] Makes the bash completion script try *bash* completions before simple, filetype completions when a git completion is not found. If bash, completions aren't available, the default file completions are used. This, behavior was inspired by Mercurial's bash completion script Ted Pavlic
2009-01-13 16:38 ` Shawn O. Pearce [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=20090113163816.GR10179@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=ted@tedpavlic.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).