From: Jon Forrest <nobozo@gmail.com>
To: git@vger.kernel.org
Subject: [ANN] Pro Git Reedited - a New Version of the Pro Git Book
Date: Mon, 02 Dec 2013 20:29:43 -0800 [thread overview]
Message-ID: <l7jmo9$1lj$1@ger.gmane.org> (raw)
When I started learning Git, I spent a fair amount of time
reading Pro Git. I found that it was a 2 steps forward, 1
step back experience. By this I mean I’d learn a couple of
new things but then I’d either read something I didn’t
understand, or else I’d realize that my previous
understanding was wrong. But, once I developed a better
understanding of Git, I went back to re-read the sections
that I didn’t previously understand. I’d almost always think
to myself that if only this word or that phrase could be
changed slightly, the concept would have been much easier to
understand. This happens to me a lot when reading technical
books.
Given that Scott was generous enough to release Pro Git as a
free book with the manuscript sources available at GitHub, I
decided to return the favor by doing a complete edit in an
attempt to improve the areas I had trouble with and to
generally tighten up the text. I’ve fed all these changes
back to the maintainer of Pro Git via GitHub pull requests.
He’s free to decide what he wants to do with them. Meanwhile,
I've published my own version of this book, which I call
Pro Git Reedited.
The PDF version of Pro Git Reedited is at
https://www.dropbox.com/s/4awq55350ef235m/progitreedited.en.pdf
and the source code is at
https://github.com/nobozo/progitreedited
I welcome your feedback. Please send any comments to me at
nobozo@gmail.com. To make sure I recognize them as
comments about this book, please include [PGR] in the
subject.
Jon Forrest
nobozo@gmail.com
reply other threads:[~2013-12-03 4:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='l7jmo9$1lj$1@ger.gmane.org' \
--to=nobozo@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).