From: Scott Chacon <schacon@gmail.com>
To: Dun Peal <dunpealer@gmail.com>
Cc: Jakub Narebski <jnareb@gmail.com>,
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 15:56:08 +0000 [thread overview]
Message-ID: <AANLkTikTEcPqeGtLEFKMCsiv9zC7Jj-E_3mrjDrR7fJR@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=wdWkZCyg6vHOaDZS=oeWAX_EhCgOLFGJOwC9G@mail.gmail.com>
Hey,
On Fri, Nov 19, 2010 at 3:47 PM, Dun Peal <dunpealer@gmail.com> wrote:
> On Fri, Nov 19, 2010 at 3:44 PM, Jakub Narebski <jnareb@gmail.com> wrote:
>> "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
>
> Wow, that's pretty cool. Any idea how often the online version at
> http://progit.org is synced with the github version?
I merge it in and push changes every month or so now. It was more
often, but the errata and translations are coming in less frequently.
I have a number of pull requests pending, mostly for formatting fixes
and translation additions. I'll probably do another merge/push around
Thanksgiving.
Scott
next prev parent reply other threads:[~2010-11-19 15:57 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
2010-11-19 15:47 ` Dun Peal
2010-11-19 15:56 ` Scott Chacon [this message]
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=AANLkTikTEcPqeGtLEFKMCsiv9zC7Jj-E_3mrjDrR7fJR@mail.gmail.com \
--to=schacon@gmail.com \
--cc=dunpealer@gmail.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--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).