git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] git.c: show usage for accessing the git(1) help page

From
Philip Oakley <philipoakley@iee.org>
Date
May 15, 2019, 06:36 UTC
Message-ID
<78710149-4e0c-01a1-ccbf-592adadbfd08@iee.org>
In-Reply-To
<20190515001717.GA138048@google.com>
Hi Emily,
On 15/05/2019 01:17, Emily Shaffer wrote:
Show 27 quoted lines
> On Tue, May 14, 2019 at 04:24:50PM +0100, Philip Oakley wrote:
>> It is not immediately obvious how to use the `git help` system
>> to show the git(1) page, with all its background and ccordinating
>> material, such as environment variables.
>>
>> Let's simply list it as the last few words of the last usage line.
>>
>> Signed-off-by: Philip Oakley <philipoakley@iee.org>
>> ---
>> This follows from the discussion <3cd065d1-9db5-f2e6-ddff-aa539746d45e@iee.org>
>> ---
>>   git.c | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/git.c b/git.c
>> index 2324ac0b7e..9a852b09c1 100644
>> --- a/git.c
>> +++ b/git.c
>> @@ -33,7 +33,7 @@ const char git_usage_string[] =
>>   const char git_more_info_string[] =
>>   	N_("'git help -a' and 'git help -g' list available subcommands and some\n"
>>   	   "concept guides. See 'git help <command>' or 'git help <concept>'\n"
>> -	   "to read about a specific subcommand or concept.");
>> +	   "to read about a specific subcommand or concept. Or use 'git help git'.");
> I'm not sure the wording makes sense here. It sounds like you're saying,
> "Or use 'git help git' to read about specific subcommands or concepts."
> which isn't really what I think you're trying to say.
True.
>
> What about, "Or, use 'git help git' for a detailed guide of the Git
> system as a whole."

I had thought about a longer sentence, but was squeezing it in, given that we (I) had to add in the other parts of that help footnote...

>
> (I'm still not sure that's quite it - since `git help git` mostly
> details the flags you can pass to git before invoking a subcommand. But
> I'm not sure that `git --help` is the place to say that...)

It's more that we are updating the system's response to a misunderstood command, hopefully with something that includes a link to our putative top level man page. It's tricky to get to without already knowing it's there.

Show 7 quoted lines
>
>>   
>>   static int use_pager = -1;
>>   
>> -- 
>> 2.21.0.windows.1.1517.gbad5f960a3.dirty
>>
Philip
Previous: Philip Oakley
Message 19 of 19 in “git --help not actually showing the git(1) help page..”
  1. Philip OakleyMay 13, 2019
  2. Jeff KingMay 13, 2019
  3. Philip OakleyMay 13, 2019
  4. Junio C HamanoMay 13, 2019
  5. Philip OakleyMay 14, 2019
  6. git.c: show usage for accessing the git(1) help pagePhilip Oakley, May 14, 2019
  7. Emily ShafferMay 15, 2019
  8. Jeff KingMay 15, 2019
  9. Philip OakleyMay 15, 2019
  10. git.c: show usage for accessing the git(1) help pagePhilip Oakley, May 15, 2019
  11. Eric SunshineMay 15, 2019
  12. 0/2 accessing the git(1) help pagePhilip Oakley, May 15, 2019
  13. 1/2 git.c: show usage for accessing the git(1) help pagePhilip Oakley, May 15, 2019
  14. 2/2 Doc: git.txt: remove backticks from link and add git-scm.com/docsPhilip Oakley, May 15, 2019
  15. Junio C HamanoMay 16, 2019
  16. Philip OakleyMay 16, 2019
  17. Jeff KingMay 16, 2019
  18. Philip OakleyMay 16, 2019
  19. Philip OakleyMay 15, 2019

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.