From: jidanni@jidanni•org
To: git@vger•kernel.org
Subject: some git-commands --help don't act like git commands --help
Date: Mon, 29 Dec 2008 14:25:51 +0800 [thread overview]
Message-ID: <87iqp333bk.fsf@jidanni.org> (raw)
Hmmm, some git-commands --help act just like git commands --help,
$ git commit --help 2>&1|wc -l
336
$ git-commit --help 2>&1|wc -l
336
But others don't
$ git am --help 2>&1|wc -l
152
$ git-am --help 2>&1|wc -l
19
$ git --version
git version 1.5.6.5
on Debian sid.
next reply other threads:[~2008-12-29 6:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-29 6:25 jidanni [this message]
2008-12-29 8:53 ` some git-commands --help don't act like git commands --help Nanako Shiraishi
2008-12-29 9:48 ` Michael Gaber
2008-12-29 9:54 ` Junio C Hamano
2008-12-29 19:37 ` "git-whatever" the new style vs. "git whatever"? jidanni
2008-12-29 20:47 ` Boyd Stephen Smith Jr.
2008-12-29 21:27 ` A Large Angry SCM
2008-12-29 22:22 ` jidanni
2008-12-29 23:19 ` jidanni
-- strict thread matches above, loose matches on Subject: below --
2008-12-29 10:29 some git-commands --help don't act like git commands --help Nanako Shiraishi
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=87iqp333bk.fsf@jidanni.org \
--to=jidanni@jidanni$(echo .)org \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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