From: Junio C Hamano <gitster@pobox.com>
Date: Mon, 11 Mar 2013 21:50:31 GMT
Subject: Re: [PATCH/RFC] Make help behaviour more consistent
Message-ID: <7vhakh8v2w.fsf@alter.siamese.dyndns.org>
In-Reply-To: <CD3017A6746B45FE8A5F242E4C597B51@PhilipOakley>

"Philip Oakley" <philipoakley@iee.org> writes:

> From: "Junio C Hamano" <gitster@pobox.com>
>> Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> writes:
>>
>>>   See 'git help git' for general help about Git.
>>>
>>> to the output of "git help"?
>> ...
>> That sounds like a good direction to go in.
>
> My earlier attempt, and Junio's reply
> http://thread.gmane.org/gmane.comp.version-control.git/217352

Yeah, I threw "git help git" in the general category of "git help
<cmd>" in that message, and now I realize that it may arguably be
confusing to some people.

Perhaps spend one more line to do something like this?

    'git help -a' and 'git help -g' lists available subcommands and
    concept guides. See 'git help <command>' or 'git help <concept>'
    to read about a specific subcommand or concept.
    For an overview, see 'git help git'.

I am neutral between the above and this:

    For an overview, see 'git help git'.
    'git help -a' and 'git help -g' lists available subcommands and
    concept guides. See 'git help <command>' or 'git help <concept>'
    to read about a specific subcommand or concept.

Hrm?