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

Re: [PATCH 0/5] git help: group common commands by theme

From
Sébastien Guimmara <sebastien.guimmara@gmail.com>
Date
May 15, 2015, 14:37 UTC
Message-ID
<555604A2.6080204@gmail.com>
In-Reply-To
<xmqqa8x6khlr.fsf@gitster.dls.corp.google.com>
On 05/14/2015 10:51 PM, Junio C Hamano wrote:
Show 14 quoted lines
> Sébastien Guimmara  <sebastien.guimmara@gmail.com> writes:
>
>> This v6 is very similar in content to the v5 [1], except minor formatting
>> adjustments in 'git help' output and recommendations from Eric.
>>
>> The major change is in the patch series itself. Commits have been
>> reordered and adjusted so that each 'apply' doesn't break the build, and
>> preserve bisectability.
>
> Hmph, did you decide to abandon the "whitespace fix" patch?  This
> does not seem to be based on that one, and it would be crazy to
> have these pa beltches *and* the other one as independent two topics
> and expect them to be merged cleanly later.
>

My mistake : I believed the preparatory patch and the new series had to be independent, and thus had to be merged in your own tree. I will correct this.

Thanks
Previous: Junio C Hamano
Message 12 of 12 in “git help: group common commands by theme”
  1. 0/5 git help: group common commands by themeSébastien Guimmara, May 14, 2015
  2. 1/5 command-list.txt: prepare with [commands] headerSébastien Guimmara, May 14, 2015
  3. 2/5 command-list.txt: add with [common] blockSébastien Guimmara, May 14, 2015
  4. 3/5 generate-cmdlist: parse common group commandsSébastien Guimmara, May 14, 2015
  5. Junio C HamanoMay 14, 2015
  6. Eric SunshineMay 14, 2015
  7. Sébastien GuimmaraMay 15, 2015
  8. 4/5 command-list.txt: drop the common- prefixSébastien Guimmara, May 14, 2015
  9. 5/5 help.c: output the typical Git workflowSébastien Guimmara, May 14, 2015
  10. 5/5 help.c: output the typical Git workflowSébastien Guimmara, May 14, 2015
  11. Junio C HamanoMay 14, 2015
  12. Sébastien GuimmaraMay 15, 2015

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.