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

Re: [PATCH 1/2] Documentation/branch: split description into subsections

From
Sverre Rabbelier <srabbelier@gmail.com>
Date
Jan 31, 2011, 01:55 UTC
Message-ID
<AANLkTin0M=K2OS2SmFWBGj3nasVzQY91Uectz+B1vsCm@mail.gmail.com>
In-Reply-To
<20110130213355.GB10039@burratino>
Heya,
2011/1/30 Jonathan Nieder <jrnieder@gmail.com>:
> Add headings for each form of the "git branch" command.  Hopefully
> this will make the description easier to read straight through without
> getting lost and help technical writers to see what needs improvement
> in the treatment of each form.

I like it. Thought for the future: it would be nice if at a sprint or such we can read through and fix the rest of the documentation in a similar way.

-- 
Cheers,

Sverre Rabbelier
Previous: Jonathan NiederNext: Jonathan Nieder
Message 5 of 9 in “Remote branchs -- how can I check them out?”
  1. João Paulo Melo de SampaioJan 30, 2011
  2. Konstantin KhomoutovJan 30, 2011
  3. 0/2 Re: Remote branchs -- how can I check them out?Jonathan Nieder, Jan 30, 2011
  4. 1/2 Documentation/branch: split description into subsectionsJonathan Nieder, Jan 30, 2011
  5. Sverre RabbelierJan 31, 2011
  6. 2/2 Documentation/branch: briefly explain what a branch isJonathan Nieder, Jan 30, 2011
  7. Junio C HamanoJan 31, 2011
  8. João Paulo Melo de SampaioJan 31, 2011
  9. Jakub NarebskiJan 30, 2011

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.