From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: Support "git cmd --help" syntax
Date: Wed, 19 Apr 2006 23:40:23 +0200 [thread overview]
Message-ID: <e26anq$42t$1@sea.gmane.org> (raw)
In-Reply-To: Pine.LNX.4.64.0604151402470.3701@g5.osdl.org
Linus Torvalds wrote:
> [...] You can always get the usage
> message with "git commit --huh?", so it's not like you've lost anything.
Or "git commit --usage".
--
Jakub Narebski
Warsaw, Poland
prev parent reply other threads:[~2006-04-19 21:40 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
2006-04-16 1:24 ` Junio C Hamano
2006-04-19 21:40 ` Jakub Narebski [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='e26anq$42t$1@sea.gmane.org' \
--to=jnareb@gmail.com \
--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).