From: "J. Bruce Fields" <bfields@fieldses.org>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: Wine + GIT
Date: Tue, 6 Dec 2005 12:39:09 -0500 [thread overview]
Message-ID: <20051206173909.GE17457@fieldses.org> (raw)
In-Reply-To: <7vacfe2ks1.fsf@assigned-by-dhcp.cox.net>
On Tue, Dec 06, 2005 at 09:33:02AM -0800, Junio C Hamano wrote:
> There is a long time-horizon plan to move most of the things out
> of /usr/bin/, and codewise we have the infrastructure to do it
> today. The only reason we haven't done so is that it would break
> scripts written by people who learned git from documents that
> tell them to write things in dash form, "git-diff".
I've enjoyed getting tab completions without having to add whatever's
required to my .bashrc to teach it about git subcommands. Oh well, I'll
get over it.
I suppose the git-subcommand convention will continue for the purpose of
naming manpages?
--b.
next prev parent reply other threads:[~2005-12-06 17:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-05 23:29 Wine + GIT Mike McCormack
2005-12-06 2:03 ` Jeff Garzik
2005-12-06 2:26 ` Junio C Hamano
2005-12-06 17:08 ` J. Bruce Fields
2005-12-06 17:33 ` Junio C Hamano
2005-12-06 17:39 ` J. Bruce Fields [this message]
2005-12-06 17:53 ` Jon Loeliger
2005-12-06 21:22 ` git shorthands (was: Re: Wine + GIT) Andreas Ericsson
2005-12-07 0:56 ` Wine + GIT Ben Clifford
2005-12-06 19:01 ` Jeff Garzik
2005-12-06 19:06 ` Mike McCormack
2005-12-06 2:18 ` Jeff Garzik
2005-12-06 23:08 ` Nick Hengeveld
2005-12-06 23:27 ` Andreas Ericsson
2005-12-06 9:02 ` Marco Costalba
-- strict thread matches above, loose matches on Subject: below --
2005-12-08 7:30 linux
2005-12-08 9:29 ` Fredrik Kuivinen
2005-12-08 18:17 ` Junio C Hamano
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=20051206173909.GE17457@fieldses.org \
--to=bfields@fieldses.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).