From: Linus Torvalds <torvalds@osdl.org>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: Support "git cmd --help" syntax
Date: Sat, 15 Apr 2006 14:07:21 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0604151402470.3701@g5.osdl.org> (raw)
In-Reply-To: <7vsloeef0k.fsf@assigned-by-dhcp.cox.net>
On Sat, 15 Apr 2006, Junio C Hamano wrote:
>
> Tried "git commit --help" with and without the patch?
I get a usage message without the patch.
With the patch, I get the man-page.
IOW, I don't see your point.
I'd have expected that to be an improvement. You can always get the usage
message with "git commit --huh?", so it's not like you've lost anything.
Now, if you have _not_ done
make prefix=/usr/share install-doc
or similar, then yes, you get something less than helpful (along the lines
of "No manual entry for git-commit"), and I agree that we could/should
improve on that somehow.
Linus
next prev parent reply other threads:[~2006-04-15 21:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-15 18:13 Support "git cmd --help" syntax Linus Torvalds
2006-04-15 20:54 ` Junio C Hamano
2006-04-15 21:07 ` Linus Torvalds [this message]
2006-04-16 1:24 ` Junio C Hamano
2006-04-19 21:40 ` Jakub Narebski
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=Pine.LNX.4.64.0604151402470.3701@g5.osdl.org \
--to=torvalds@osdl.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).