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

Re: Best newbie / advanced / expert reference texts for Git?

From
KKKonstantin Khomoutov <flatworm@users.sourceforge.net>
Date
Nov 19, 2010, 14:53 UTC
Message-ID
<20101119175354.350f982f.kostix@domain007.com>
In-Reply-To
<AANLkTin_kS_2d=ajuGo-V_OWsF91xSb=SeKmrX9Aghe8@mail.gmail.com>

On Fri, 19 Nov 2010 11:38:26 +0000 Dun Peal <dunpealer@gmail.com> wrote:

Show 6 quoted lines
>> Check out http://progit.org/.  I am not affiliated with the author
>> (s) or the web site. I just stumbled across it a couple of weeks
>> ago when I went to set up a git server for our group. It seems to
>> answer every question I've ever had about git, and then some. 
> Thanks; sounds like it should serve well for the Advanced and possibly
> Intermediate categories. Still need a good text for the Newbie class.

http://git-scm.com/course/svn.html http://stackoverflow.com/questions/1042280/a-subversion-users-guide-to-git and http://www.google.com/search?q=git+for+svn+users in general.

Also there's a very good DVCS introductory writing for real newbies which deals with concepts rather than commands -- http://tom.preston-werner.com/2009/05/19/the-git-parable.html

Previous: Dun PealNext: Jakub Narebski
Message 4 of 11 in “Best newbie / advanced / expert reference texts for Git?”
  1. Dun PealNov 19, 2010
  2. Patrick DoyleNov 19, 2010
  3. Dun PealNov 19, 2010
  4. Konstantin KhomoutovNov 19, 2010
  5. Jakub NarebskiNov 19, 2010
  6. Dun PealNov 19, 2010
  7. Scott ChaconNov 19, 2010
  8. Scott ChaconNov 19, 2010
  9. Dun PealNov 19, 2010
  10. Scott ChaconNov 19, 2010
  11. Nguyen Thai Ngoc DuyNov 19, 2010

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.