From: Matthieu Moy <Matthieu.Moy@imag.fr>
To: "Stefan Näwe" <stefan.naewe+git@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Wrong help text on git status -h ?
Date: Wed, 23 Apr 2008 18:00:47 +0200 [thread overview]
Message-ID: <vpqfxtc36j4.fsf@bauges.imag.fr> (raw)
In-Reply-To: <loom.20080423T125136-135@post.gmane.org> ("Stefan Näwe"'s message of "Wed\, 23 Apr 2008 12\:54\:51 +0000 \(UTC\)")
Stefan Näwe <stefan.naewe+git@gmail.com> writes:
> Getting help for commit on 'git status -h' can't be right, can it ?
> Or am I missing something?
I'd say: both.
git status could have been spelled "git commit --dry-run", they're
actually the same command, but "git status" stops before launching the
editor and doing the actual commit. So, they take the exact same set
of options.
That said, in an ideal world, "git status -h" would mention that the
commit message options are ignored with "git status".
--
Matthieu
next prev parent reply other threads:[~2008-04-23 16:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-23 12:54 Wrong help text on git status -h ? Stefan Näwe
2008-04-23 16:00 ` Matthieu Moy [this message]
2008-05-13 11:09 ` Stefan Näwe
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=vpqfxtc36j4.fsf@bauges.imag.fr \
--to=matthieu.moy@imag.fr \
--cc=git@vger.kernel.org \
--cc=stefan.naewe+git@gmail.com \
/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).