From: Junio C Hamano <junkio@cox.net>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: git@vger.kernel.org
Subject: Re: Wine + GIT
Date: Tue, 06 Dec 2005 09:33:02 -0800 [thread overview]
Message-ID: <7vacfe2ks1.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20051206170803.GD17457@fieldses.org> (J. Bruce Fields's message of "Tue, 6 Dec 2005 12:08:03 -0500")
"J. Bruce Fields" <bfields@fieldses.org> writes:
> On Mon, Dec 05, 2005 at 09:03:31PM -0500, Jeff Garzik wrote:
>> 2) The "git-foo" commands are apparently uncool. "git foo ..." is
>> preferred.
>
> How does e.g. git-diff differ from git diff? I thought they were
> equivalent.--b.
For now, but to futureproof your document and its readers, it is
better spelled as "git frotz" not "git-frotz".
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".
next prev parent reply other threads:[~2005-12-06 17:33 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 [this message]
2005-12-06 17:39 ` J. Bruce Fields
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=7vacfe2ks1.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=bfields@fieldses.org \
--cc=git@vger.kernel.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).