From: Patrick Doyle <wpdster@gmail.com>
To: Dun Peal <dunpealer@gmail.com>
Cc: Git ML <git@vger.kernel.org>
Subject: Re: Best newbie / advanced / expert reference texts for Git?
Date: Fri, 19 Nov 2010 06:18:36 -0500 [thread overview]
Message-ID: <AANLkTik5ZYC66NicUvbDxJMiR_0iK3vPRAf9dGAQu+qW@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikctrASqX0FLCOapyJCt1VqG6_cxs_oXJ6fExZC@mail.gmail.com>
On Fri, Nov 19, 2010 at 6:02 AM, Dun Peal <dunpealer@gmail.com> wrote:
> Hi there,
>
> What are the best texts for the following three levels of knowledge:
>
> 1. Newbie: someone who used a simple, centralized SCM (such as SVN)
> but never touched Git.
> 2. Intermediate: someone who uses Git's simpler features, and can do
> simple branching/merging, but would like to fully understand the
> underlying concepts such as the DAG, and master all common user-level
> operations such as branching, merging, and rebasing.
> 3. Advanced: someone who knows all the above, but would like to know
> everything there is to know about Git.
>
> The target audience in my particular case is smart, with strong CS
> background, especially those in the two latter categories.
>
> Being available online is a plus, but will not disqualify a good
> offline reference.
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.
--wpd
next prev parent reply other threads:[~2010-11-19 11:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-19 11:02 Best newbie / advanced / expert reference texts for Git? Dun Peal
2010-11-19 11:18 ` Patrick Doyle [this message]
2010-11-19 11:38 ` Dun Peal
2010-11-19 14:53 ` Konstantin Khomoutov
2010-11-19 15:44 ` Jakub Narebski
2010-11-19 15:47 ` Dun Peal
2010-11-19 15:56 ` Scott Chacon
2010-11-19 15:54 ` Scott Chacon
2010-11-19 17:08 ` Dun Peal
2010-11-19 17:20 ` Scott Chacon
2010-11-19 12:14 ` Nguyen Thai Ngoc Duy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AANLkTik5ZYC66NicUvbDxJMiR_0iK3vPRAf9dGAQu+qW@mail.gmail.com \
--to=wpdster@gmail.com \
--cc=dunpealer@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).