We try to keep our books accurate, but sometimes mistakes creep in. This page lists the errors submitted by our astute readers. If you've found a new error, please submit it.

The latest version of the book is P3.0, released almost 2 years ago. If you've bought a PDF of the book and would like to upgrade it to this version (for free), visit your home page.

Key: Typo Tech. Error Suggestion Not a problem Next edition

By default this page displays the errata for the latest version of the book. If you have a previous version, select it here:  

(To find out what version you have, look at the copyright page, a few pages in from the front of the book. If it says (say) 'Second Printing', then here it'll be P2.0. If there are interim PDF releases in that printing, they'll be 2.1, 2.2, and so on.)

PDF Paper Description Found in Fixed in
12

#49711: This is in the ePub version of the book. Throughout the book "(as yet) unwri--Melissa Chase

P3.0
18-Aug-12
12
#49712: This problem appears throughout the ePub version of the book: the phrase "(as yet) unwritten content" seems to have crept in from some early v...more...
P3.0
18-Aug-12
12

#49713: Just rebuilt the ePub of the book at it's fine. The problem been with the version that had been pushed to my DropBox account.--Melissa Chase

P3.0
18-Aug-12
44
#53011: Sorry, my paper edition of the book isn't listed in the Version dropdown. (On the copyright page, I have "P2.0 March 2009" and "Version: 2009...more...
P2.0
07-Oct-13
45
#50093: You have described the use of git rebase command.If we want to rebase RB_1.0 on top of master then command should have been prompt> git che...more...
P3.0
31-Oct-12
95
#49291: Third paragraph in Section 7.3: Keeping up to date "Fetching changes updates your remote branches." should be "Fetching changes updates yo...more...
P1.0
07-May-12

Stuff To Be Considered in the Next Edition

PDF Paper Description Found in Fixed in
1
#36685: No mention seems to be made of the .gitattributes file. We are coming from Subversion and we use RCS $Header$ ids -- pointers on how to get t...more...
P1.0
28-Dec-08
43
#36647: "git commit -a" launches a terminal-based editor that I'm not familiar with. More explanation required here for the newbie. Is this a configur...more...
P1.0
27-Dec-08
43
#44227: This is clearly an error I get the following $ git commit -a Aborting commit due to empty commit message. the book shows the output as ...more...
Travis Swicegood says: This is due to no changes be made to the working tree. It's possible this could be made more clear, so I'm keeping this open as something to consider for a future edition.
P2.0
22-Jul-10
45
#39566: You describe the process of tagging a release and cleaning up your repository by rebasing master on top of your release branch and deleting th...more...
Travis Swicegood says: There should be more clarification on when it's ok to run rebase and not. Keeping this open for consideration in the next edition.
P2.0
19-Jun-09
45
#46043: The text says the "<meta> description" change that was added to the RB 1.0 branch needs to be added to the master branch too (by using git reb...more...
P2.0
17-Dec-10
45
#40163: Regarding this statement : "Right now your repository looks like Figure 3.1. After rebasing, it looks like Figure 3.2, on the following page."...more...
P2.0
24-Jul-09
52
#37275: Chapter 3 leaves the work area (/work/mysite) in branch RB_1.0.1. (p. 46) Chapter 4 assumes the work area has master checked out, that may be...more...
P1.0
25-Jan-09
73

#37305: prompt> git reset --hard HEAD^
doesn't work on Windows (I'm prompted with: More?).
Adding quotes around "HEAD^" solves the issue.--Marnix

P1.0
27-Jan-09
78
#43349: When git branch -d or git branch -D deletes a branch, is the branch gone forever? Later in the book, I see branches retrieved using tags that ...more...
Travis Swicegood says: Need to clarify what a branch really is. Since it's simply a file pointing to a commit and commits that are part of a tree of commits never go away, the "branch" is never really gone (nor really there, if you want to wax philosophical about it).
P2.0
20-May-10
84
#38818: At the end of the page, when you talk about the caret (^). Although what it says is correct, it's not complete. The most important use of t...more...
Travis Swicegood says: Excellent point. Marking this as Next Edition so I remember to come back to it when we get around to a 2nd Edition.
P1.0
10-Apr-09
94
#42112: 'git reset' with neither --soft or --hard leaves the changes in the working tree. I think the fourth paragraph would be clearer if it read so...more...
Travis Swicegood says: Marking for next edition. There's definitely some room for improvement, but what's there now is factually correct---albeit in need of more context.
P2.0
19-Jan-10
98
#45441: On page 98, the sidebar "Adding a Remote Repository Later" is incomplete... well, ok, wrong. At least, it doesn't work for me. Here is a (...more...
Travis Swicegood says: This should explain how to get the remote repository. Here, Charles, assumed that step was inherent in the process as explained (it's not).
P2.0
26-Oct-10
103
#38706: At the very bottom of page 103, the example at the very bottom should be: git checkout -b another-from-1.0 1.0 The trailing tag name has bee...more...
Travis Swicegood says: The tag in this case is the current commit, so the operations are identical. Marking as Next Edition to revisit in the 2nd edition to see if it can be clarified.
P1.0
03-Apr-09
103

#36480: another workable URL would be
ssh://git@github.com/tswicegood/mysite-chp6.git--Steven Finnegan

P1.0
17-Dec-08
103
#36481: It would be helpful to show the various URL formats that work, such as: "git clone sjf@hercules:git-test/depot depot-frm-svr", "git clo...more...
P1.0
17-Dec-08
108
#43351: Even after the discussion of remote repository handling, I'm left confused. I've seen discussion of remote/ branches in the local repository, ...more...
Travis Swicegood says: Excellent feedback that I've marked for the next edition. Will revisit to make sure I clarify this chapter.
P2.0
20-May-10
111
#39914: The command "git tag contacts/1.1 contacts" fails with the error "fatal: Failed to resolve 'contacts' as a valid ref.' since the contacts bran...more...
Travis Swicegood says: Marking for next edition as this would change *all* chapters (and/or repositories). There needs to be a command to run that will create local branches for all of the remote branches.
P2.0
10-Jul-09
114
#37327: At the end of section 8.2, you allude to the realization that you should have branched earlier, and suggest creating a branch from an earlier ...more...
P1.0
28-Jan-09
150
#39280: Not really the linux admin, but as far as I could infer from the manpages, the adduser command on page 150 is not right. In the text, there...more...
Travis Swicegood says: This was the tested and verified method when the book was published. Will revisit and include version information in the next edition.
P2.0
30-May-09
151
#47811: I have found that the post-update hook is not (necessarily) executable by default on a few installations both using the python install method ...more...
P2.0
24-Oct-11
155
#43356: You're using sudo to run the git daemon as user git to serve up a repository owned by user git. What prevents the daemon from modifying the re...more...
P2.0
20-May-10
155
#43357: "The final & suffix detaches it from the current session, and the nohup prefix detaches it from the current user." & creates a new process ...more...
Travis Swicegood says: I'm leaving this open for consideration in the next edition. This is technically correct and I should probably mention it in a footnote, but for all intents and purposes, the explanation in the book is ok for a mental model.
P2.0
20-May-10
160
#43358: Please also include 'recipes' for reverting a previous commit in history, reverting a range of previous commits in history, and reverting (one...more...
P2.0
20-May-10