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

Re: [DRAFT 2] Branching and merging with git

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Dec 4, 2006, 10:56 UTC
Message-ID
<Pine.LNX.4.63.0612041153330.28348@wbgn013.biozentrum.uni-wuerzburg.de>
In-Reply-To
<20061204072350.GC28043@fieldses.org>
Hi,
On Mon, 4 Dec 2006, J. Bruce Fields wrote:
> So I'm trying to split out an extremely concise "quick-start" guide 
> (modelled partly on Mercurial's) that doesn't even pretend to explain 
> anything,
you might want to look at the QuickStart page in Git's wiki...
Show 8 quoted lines
> 	  	1. clone
> 		2. checking out old versions, basic branch management
> 		3. keeping up-to-date with fetch
> 		4. bisect
> 		5. archaeology (commits DAG, git-log, ...)
> 		6. creating commits, index file
> 		7. resolving merges, pull
> 		8. publishing a public repository, push

Another approach would be to illustrate short stories of a failed merge, or "how I put up a public repository", etc. Like, more example-based (and of course short enough that people actually read through it).

Ciao, Dscho

Previous: J. Bruce FieldsNext: Jakub Narebski
Message 8 of 11 in “Re: [DRAFT] Branching and merging with git”
  1. Junio C HamanoNov 18, 2006
  2. [DRAFT 2] Branching and merging with gitlinux@horizon.com, Nov 20, 2006
  3. 1/2 Branching and merging with gitJunio C Hamano, Nov 22, 2006
  4. 2/2 Branching and merging with gitJunio C Hamano, Nov 22, 2006
  5. Rene ScharfeNov 22, 2006
  6. J. Bruce FieldsDec 4, 2006
  7. J. Bruce FieldsDec 4, 2006
  8. Johannes SchindelinDec 4, 2006
  9. Jakub NarebskiDec 15, 2006
  10. J. Bruce FieldsDec 15, 2006
  11. Junio C HamanoNov 22, 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.