From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Shawn O. Pearce" <spearce@spearce.org>,
Christian Couder <chriscool@tuxfamily.org>,
git@vger.kernel.org
Subject: Re: git-browse-help?
Date: Sat, 15 Dec 2007 06:01:53 -0500 [thread overview]
Message-ID: <20071215110153.GA3447@coredump.intra.peff.net> (raw)
In-Reply-To: <20071215100811.GA1692@coredump.intra.peff.net>
On Sat, Dec 15, 2007 at 05:08:11AM -0500, Jeff King wrote:
> On Fri, Dec 14, 2007 at 09:38:05AM -0800, Junio C Hamano wrote:
>
> > > Should it perhaps be "git--browse-help" or "git-help--browse" to follow
> > Good eyes and a sensible argument. Go wild.
>
> Looks like you beat me to it. Thanks.
Although I would have called it "git-help--browse" rather than
"git-browse--help" since
a) it is related to "git help", not "git browse"
b) there is no tab completion conflict with git-he, but there is with
git-br. :) This is of course because I am using the file
completion, but the programmable bash completion has the same
problem. Shawn, perhaps it should simply ignore *--* as plumbing?
I can prepare a patch if "git-help--browse" makes more sense.
-Peff
next prev parent reply other threads:[~2007-12-15 11:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-14 9:28 git-browse-help? Jeff King
2007-12-14 17:38 ` git-browse-help? Junio C Hamano
2007-12-15 10:08 ` git-browse-help? Jeff King
2007-12-15 11:01 ` Jeff King [this message]
2007-12-15 11:11 ` git-browse-help? Jeff King
2007-12-15 19:25 ` git-browse-help? Junio C Hamano
2007-12-15 22:25 ` git-browse-help? Shawn O. Pearce
2007-12-15 19:26 ` git-browse-help? Junio C Hamano
2007-12-16 7:21 ` git-browse-help? Jeff King
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=20071215110153.GA3447@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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 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).