Errata for Pragmatic Guide to Git

The "report erratum" link at the bottom of the pages should take us to the web page of _all_ errata, not to the form where we report one error. At the bottom of the errata web page should be the form to submit one that hasn't been reported yet. Or maybe the form should be at the top of the list. At least give us a chance to see what others have reported before submitting a new defect.

The way it's set up now, the conscientious reader will feel frustrated that he wasted so much time crafting a good error report. He will also feel annoyed that he reported the same error as so many others. Many of your potential error reporters will decide never to report another error.--bob desinger

In the who is this book for? section
This book is geared for someone new to Git who is looking
to get up to speed quickly. This book is for you if you’re
status.untracked.start familiar with another VCS such as
Subversion and are looking for a quick guide to the Git
landscape or if you’re a quick study and want a concise
guide.

Not sure how the status.untracked.start got into the paragraph.--Gary McCormack

Introduction - Who Is This Book For?
The second sentence in both epub and PDF contains "status.untracked.start":

...if you're status.untracked.start familiar...--David J. Schmidt

In Windows (at least on XP) with msysgit,
git config user.name "Your Name"
fails with the error
error: could not lock config file .git/config: No such file or directory
I note that the Windows Explorer GUI won't let me create a directory named ".git".
But I can create .git in the msysgit shell:
mkdir .git
Then the original command
git config user.name "Your Name"
succeeds.

In the sentence at the start of the 3rd paragraph, "There are a few limitations to this type of repository clone," it is not clear that it is referring to shallow repositories instead of cloned repositories. I'd suggest it say something like "There are a few limitations to shallow repository clones." --Tom

I think some markup appears as part of the text by mistake - "This book is for you if you’re status.untracked.start familiar with another VCS"--Stuart Blair

The first example is fine, it reads "git fetch <remote name>". The second example confuses me. It reads "git fetch remote local branch:remotes/remote/remote branch". I am still learning git, so not entirely sure what this should be. But it does appear obvious that <> symbols are missing, and that would help clarify what is meant. For example, did the author intend to write this? "git fetch remote <local branch>:remotes/remote/<remote-branch>" ?--Justin

Developers using Xcode on Mac now have git installed by default in /usr/local/git. I think they started doing this fairly recently. The latest Xcode setup installs git version 1.7.1.--Todd Fincannon

At the bottom of the page, you start talking about "Tracking Branches" out of the blue. Does that indicate that until now you've been discussing non-tracking branches? One sentence describing non-tracking branches (or explaining that until that point, you'd been discussing non-tracking branches) would be very helpful.--Jonathan Polirer

What about working with older files and getting them out of the repository to see how a file has changed. With subversion, this is fairly intuitive, but for people who are new to the DVCS, this is a little bit out of the ordinary.

What about adding a section on comparing differences with a graphical tool? I know you support the merge scenario, but for those people who "like" those tools, they are going to want their tool for comparing differences too. Thanks!