From: Michael Gaber <Michael.Gaber@gmx.net>
To: git@vger.kernel.org
Subject: Re: some git-commands --help don't act like git commands --help
Date: Mon, 29 Dec 2008 10:48:07 +0100 [thread overview]
Message-ID: <49589CD7.4070104@gmx.net> (raw)
In-Reply-To: <20081229175305.6117@nanako3.lavabit.com>
[-- Attachment #1: Type: text/plain, Size: 816 bytes --]
Nanako Shiraishi schrieb:
> Quoting jidanni@jidanni.org:
>
>> 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
>
> Thank you for your observation; what do you want to do about it?
>
> Are you complaining that some commands do not have customized description that is not as long as the full manual page but not as terse as the short help "-h" output? Or are you complaining some other commands do not give you full manual pages for "--help"?
>
I think he just wantet to state that the output of git-command --help
and git command --help should be identical as the both do the same
thing, don't they?
Regards Michael
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3656 bytes --]
next prev parent reply other threads:[~2008-12-29 9:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-29 6:25 some git-commands --help don't act like git commands --help jidanni
2008-12-29 8:53 ` Nanako Shiraishi
2008-12-29 9:48 ` Michael Gaber [this message]
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=49589CD7.4070104@gmx.net \
--to=michael.gaber@gmx.net \
--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).