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

Re: [DRAFT] Branching and merging with git

From
JFJ. Bruce Fields <bfields@fieldses.org>
Date
Nov 19, 2006, 17:50 UTC
Message-ID
<20061119175040.GB15608@fieldses.org>
In-Reply-To
<20061117182157.GC11882@fieldses.org>
On Fri, Nov 17, 2006 at 01:21:57PM -0500, bfields wrote:
> On Fri, Nov 17, 2006 at 10:32:46AM -0500, Theodore Tso wrote:
> > It would be nice if there was an easy way to direct users through the
> > documentation in a way which makes good pedagogical sense.
....
> How about this as a strawman "git user's manual" outline:

In fact, I'm tempted to submit a patch that just assigns a chapter number to everything under Documentation/, slaps a single table of contents on the front, and calls the result "the git user's manual."

Of course, the moment people started trying to read the thing they'd complain that it was a mess--some stuff referenced without being introduced, other stuff introduced too many times. But then over time maybe that'd force us to mold it into some sort of logical sequence.

Previous: Junio C HamanoNext: Petr Baudis
Message 5 of 10 in “Re: [DRAFT] Branching and merging with git”
  1. J. Bruce FieldsNov 17, 2006
  2. linux@horizon.comNov 18, 2006
  3. Jakub NarebskiNov 18, 2006
  4. Junio C HamanoNov 18, 2006
  5. J. Bruce FieldsNov 19, 2006
  6. Git manualsPetr Baudis, Nov 19, 2006
  7. Jakub NarebskiNov 19, 2006
  8. Robin RosenbergNov 19, 2006
  9. J. Bruce FieldsNov 19, 2006
  10. Documentation: add a "git user's manual"J. Bruce Fields, Nov 26, 2006

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.