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

Re: [PATCH] Modifies the default git help message to be grouped by topic

From
Jeff King <peff@peff.net>
Date
Dec 2, 2008, 17:28 UTC
Message-ID
<20081202172848.GA19876@coredump.intra.peff.net>
In-Reply-To
<20081202172025.GB15826@coredump.intra.peff.net>
On Tue, Dec 02, 2008 at 12:20:25PM -0500, Jeff King wrote:
Show 5 quoted lines
> Sorry to reverse direction after you resubmitted, but my earlier comment
> on "this list shouldn't change frequently" didn't take into account that
> the _synopsis_ might change, which is much more likely. So maybe rather
> than ditching the auto-generation, it makes sense to just hardcode the
> order and categorization, but pull the rest from autogeneration.

Note also that one could of course just use "common:basic" or something like that in command-list.txt. But to handle arbitrary ordering, we would have to reorder command-list as appropriate (which currently gets sorted), or do something awful like common:basic1, common:basic2, etc. I tried to choose the most straightforward approach that didn't involve duplication of information.

-Peff
Previous: Jeff King
Message 3 of 3 in “Modifies the default git help message to be grouped by topic”
  1. Modifies the default git help message to be grouped by topicScott Chacon, Dec 2, 2008
  2. Jeff KingDec 2, 2008
  3. Jeff KingDec 2, 2008

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.