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
Jan 7, 2007, 23:44 UTC
Message-ID
<20070107234411.GD18009@fieldses.org>
In-Reply-To
<20070103170411.GB5491@thunk.org>
On Wed, Jan 03, 2007 at 12:04:11PM -0500, Theodore Tso wrote:
> What ever happened to this document?  There was some talk of getting
> this integrated into the git tree as Docmentation/tutorial-3.txt.
Just to throw more fuel on the fire....
I have a draft attempt at a complete "git user's manual" at
	http://www.fieldses.org/~bfields/
The goals are:
	- Readable from beginning to end in order without having read
	  any other git documentation beforehand.
	- Helpful section names and cross-references, so it's not too
	  hard to skip around some if you need to.
	- Organized to allow it to grow much larger (unlike the
	  tutorials)

It's more liesurely than tutorial.txt, but tries to stay focused on practical how-to stuff. It adds a discussion of how to resolve merge conflicts, and partial instructions on setting up and dealing with a public repository.

I've lifted a little bit from "branching and merging" (e.g., some of the discussion of history diagrams), and could probably steal more if that's OK. (Similarly anyone should of course feel free to reuse bits of this if any parts seem more useful than the whole.)

There's a lot of detail on managing branches and using git-fetch, just because those are essential even to people needing read-only access (e.g., kernel testers). I think those sections will be much shorter once the new "git remote" command and the disconnected checkouts are taken into account.

I do feel bad about adding yet another piece of documentation, but I we need something that goes through all the basics in a logical order, and I wasn't seeing how to grow the tutorials into that.

Opinions?
--b.
Previous: Junio C HamanoNext: Junio C Hamano
Message 17 of 37 in “[DRAFT] Branching and merging with git”
  1. linux@horizon.comNov 16, 2006
  2. Jakub NarebskiNov 17, 2006
  3. Jakub NarebskiNov 17, 2006
  4. Jakub NarebskiNov 17, 2006
  5. Theodore TsoNov 17, 2006
  6. SeanNov 17, 2006
  7. Nguyen Thai Ngoc DuyNov 17, 2006
  8. Marko MacekNov 17, 2006
  9. Petr BaudisNov 17, 2006
  10. SeanNov 17, 2006
  11. J. Bruce FieldsNov 17, 2006
  12. Jakub NarebskiNov 17, 2006
  13. Theodore TsoJan 3, 2007
  14. Junio C HamanoJan 3, 2007
  15. linux@horizon.comJan 4, 2007
  16. Junio C HamanoJan 4, 2007
  17. J. Bruce FieldsJan 7, 2007
  18. Junio C HamanoJan 8, 2007
  19. J. Bruce FieldsJan 8, 2007
  20. David KågedalJan 8, 2007
  21. Theodore TsoJan 8, 2007
  22. J. Bruce FieldsJan 9, 2007
  23. Andreas EricssonJan 9, 2007
  24. J. Bruce FieldsJan 9, 2007
  25. Theodore TsoJan 9, 2007
  26. J. Bruce FieldsJan 10, 2007
  27. Theodore TsoJan 8, 2007
  28. J. Bruce FieldsJan 8, 2007
  29. Jakub NarebskiJan 8, 2007
  30. Guilhem BonnefilleJan 8, 2007
  31. J. Bruce FieldsJan 9, 2007
  32. Petr BaudisNov 17, 2006
  33. SeanNov 17, 2006
  34. Petr BaudisNov 17, 2006
  35. Chris RiddochNov 17, 2006
  36. Petr BaudisNov 17, 2006
  37. SeanNov 17, 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.