Thread (1 message) 1 message, 1 author, 2016-06-15

Re: [PATCH/RFC] Make help behaviour more consistent

From: Junio C Hamano <hidden>
Date: 2016-06-15 22:56:22

"Philip Oakley" [off-list ref] writes:
From: "Junio C Hamano" <redacted>
quoted
Matthieu Moy [off-list ref] writes:
quoted
  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?
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help