From: Jakub Narebski <jnareb@gmail.com>
To: Dun Peal <dunpealer@gmail.com>
Cc: Patrick Doyle <wpdster@gmail.com>, Git ML <git@vger.kernel.org>
Subject: Re: Best newbie / advanced / expert reference texts for Git?
Date: Fri, 19 Nov 2010 07:44:13 -0800 (PST) [thread overview]
Message-ID: <m3vd3t48uy.fsf@localhost.localdomain> (raw)
In-Reply-To: <AANLkTin_kS_2d=ajuGo-V_OWsF91xSb=SeKmrX9Aghe8@mail.gmail.com>
Dun Peal <dunpealer@gmail.com> writes:
> On Fri, Nov 19, 2010 at 11:18 AM, Patrick Doyle <wpdster@gmail.com> wrote:
> > 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.
>
> P.S. I glanced at it briefly and it seemed a bit out of date, but
> perhaps my inspection was too cursory.
"Pro Git" out of date. Oh really? It is kept quite up to date (for
example adding information about "gitolite" and "smart" HTTP
transport), see https://github.com/progit/progit
As to other documentation, see
https://git.wiki.kernel.org/index.php/GitDocumentation
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2010-11-19 15:44 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
2010-11-19 11:38 ` Dun Peal
2010-11-19 14:53 ` Konstantin Khomoutov
2010-11-19 15:44 ` Jakub Narebski [this message]
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=m3vd3t48uy.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=dunpealer@gmail.com \
--cc=git@vger.kernel.org \
--cc=wpdster@gmail.com \
/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).