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

Re: [PATCH 0/3] git-help -i (info): finishing touches

From
Junio C Hamano <gitster@pobox.com>
Date
Dec 10, 2007, 10:06 UTC
Message-ID
<7v8x42n9s4.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<1197279969-10613-1-git-send-email-gitster@pobox.com>
Junio C Hamano <gitster@pobox.com> writes:
> This series attempts to add finishing touches to "git help -i" (info)
> support.

Side note. The patches I sent out are queued for 'next', and I'll push it out shortly. I am hoping, after this series graduates to 'master', to be able to tag v1.5.4-rc0 and declare 'master' as feature complete for now, and see everybody move to bugfix-only mode.

Currently, the man pages are sorted in $(wildcard) order in the main menu, but I think:

 * make git(7) the first node after Top;
 * order the commands in the main @menu to follow the command-list.txt
   categorization, and show Porcelains and then Plumbings, just like
   git(7) does;

would make the organization better, but I did not do that tonight. I'd leave that as an exercise to interested readers.

I also briefly considered rolling the manual pages into git.info which is built from the user manual, but I decided against it for now. I think the current organization of the user manual is good as a standalone document, and making the manual set as its appendix is possible but not necessary. I can be persuaded differently, though.

Next: Christian Couder
Message 1 of 3 in “Re: [PATCH 0/3] git-help -i (info): finishing touches”
  1. Junio C HamanoDec 10, 2007
  2. Christian CouderDec 11, 2007
  3. Junio C HamanoDec 11, 2007

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.