From: Philip Oakley <philipoakley@iee.org>
To: Jeff King <peff@peff.net>
Cc: Git List <git@vger.kernel.org>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Duy Nguyen <pclouds@gmail.com>
Subject: Re: git --help not actually showing the git(1) help page..
Date: Mon, 13 May 2019 22:55:47 +0100 [thread overview]
Message-ID: <a0afd3c4-93ff-31e6-a622-5751c6b5a549@iee.org> (raw)
In-Reply-To: <20190513205301.GA22745@sigill.intra.peff.net>
Hi Peff
On 13/05/2019 21:53, Jeff King wrote:
> On Mon, May 13, 2019 at 09:47:27PM +0100, Philip Oakley wrote:
>
>> Is there a cli way, especially on Git for Windows bash, to get the html man
>> page of git(1)? I have it on my system, so can go via another page but..
>>
>> All the `git <cmd> --help` appear to work, but I can't determine the correct
>> invocation for bringing up the stupid content tracker's page in the browser.
>> Previously I'd have expected either `git --help` or `git git --help` to work
>> (can't remember which). The former only produces the short form -h help in
>> the bash window, the latter says 'git' isn't a command.
> Try "git help git".
Ahh, that's the one. I'd totally forgot about that method.
>
> It might be worth mentioning it in the paragraph at the end of "git
> help".
True. I'll stick on my todo list, along with adding to the general usage
message. Possibly "Or `git help git`."
On GfW I commonly use the `git <cmd> --help` when things go wrong, so
making the response to that give the right advice would be good. (It's
almost the same isue as `git --version`).
> --
Philip
next prev parent reply other threads:[~2019-05-13 21:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-13 20:47 git --help not actually showing the git(1) help page Philip Oakley
2019-05-13 20:53 ` Jeff King
2019-05-13 21:55 ` Philip Oakley [this message]
2019-05-13 22:44 ` Junio C Hamano
2019-05-14 14:05 ` Philip Oakley
2019-05-14 15:24 ` [PATCH] git.c: show usage for accessing " Philip Oakley
2019-05-15 0:17 ` Emily Shaffer
2019-05-15 1:53 ` Jeff King
2019-05-15 6:43 ` Philip Oakley
2019-05-15 8:11 ` [PATCH v2] " Philip Oakley
2019-05-15 8:14 ` Eric Sunshine
2019-05-15 22:47 ` [PATCH v3 0/2] " Philip Oakley
2019-05-15 22:47 ` [PATCH v3 1/2] git.c: show usage for " Philip Oakley
2019-05-15 22:47 ` [PATCH v3 2/2] Doc: git.txt: remove backticks from link and add git-scm.com/docs Philip Oakley
2019-05-16 1:56 ` Junio C Hamano
2019-05-16 11:25 ` Philip Oakley
2019-05-16 22:22 ` Jeff King
2019-05-16 23:09 ` Philip Oakley
2019-05-15 6:36 ` [PATCH] git.c: show usage for accessing the git(1) help page Philip Oakley
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=a0afd3c4-93ff-31e6-a622-5751c6b5a549@iee.org \
--to=philipoakley@iee.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=pclouds@gmail.com \
--cc=peff@peff.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.