Errata
The errata list is a list of errors and their corrections that were found after the product was released.
The following errata were submitted by our customers and have not yet been approved or disproved by the author or editor. They solely represent the opinion of the customer.
Color Key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update
Version | Location | Description | Submitted by | Date submitted |
---|---|---|---|---|
Page 9 3rd para ("Debian/Ubuntu") |
Apparently, an update to what the Git package is actually called in Ubuntu -- as of Vivid Vervet, the list of packages (http://packages.ubuntu.com/vivid/devel/) claims thusly: |
Robert P. J. Day | Jul 21, 2015 | |
Page 10 Top pf page |
In the latest package list, Ubuntu now mentions a package: |
Robert P. J. Day | Jul 21, 2015 | |
Printed | Page 21 Last line |
"Initialized empty Git repository in .git/" |
Cong Liu | Jan 13, 2018 |
Printed | Page 22 Code snippet at the bottom |
" |
Cong Liu | Jan 13, 2018 |
Printed | Page 23 Code snippet at the bottom |
" |
Cong Liu | Jan 13, 2018 |
Printed | Page 23 First code snippet |
" |
Cong Liu | Jan 13, 2018 |
Page 24 bottom of page |
Isn't it true you have to |
Kenneth Lum | Feb 13, 2016 | |
Printed | Page 26 Viewing commit differences |
The diff doesn't show a difference in the line "My web site is alive!" but the original file (p21) is "My website is alive!" so either p21 or p26 are incorrect. |
Jonathan Hunt | Jul 12, 2014 |
Page 26 Top pf page |
First sentence claims that "show-branch" shows summary only "for the current development branch." Pretty sure that's not true -- man page suggests it does it for all branches: |
Robert P. J. Day | Jul 21, 2015 | |
Page 32 "Git Obejct Types" |
That section suggests that the object store contains things like "log messages" ... technically, isn't the object store the directory .git/objects? Because if it is, the log messages are stored in a sibling directory, .git/logs. Or am I missing something here? Just trying to be precise. |
Robert P. J. Day | Jul 21, 2015 | |
Printed | Page 34 3rd paragraph |
"In fact, Git does not track file or directory names, which are associated with files in secondary ways." |
Ismail Daif | Mar 22, 2019 |
Page 37-8 Figures |
Not an error so much as that the two figures (4-1 and 4-2) make no mention of the names of the files or subdirectory that is being created, which technically is fine given Git's content-based addressing, but new users might get confused looking for the filenames in those figures. |
Robert P. J. Day | Jul 27, 2015 | |
Printed | Page 40 near top |
The hash for the file "hello.txt" will change if the end-of-line character is not a linefeed. |
Michael Soyka | Mar 25, 2016 |
Printed | Page 41 Line 2 |
"40 bytes of hexadecimal" |
Cong Liu | Jan 14, 2018 |
Page 42 United States |
Such a hash function is sometimes called a digest to emphasize that it serves as a sort of summary of the hashed object. |
Kin Lum | May 02, 2014 | |
Printed, PDF | Page 43 6th paragraph ("But Git also relies...") |
This seems a bit confusing: |
Phillip Hutto | Mar 16, 2014 |
Printed | Page 44 First example under "Commits" |
The string argument for the "echo" command includes the characters "\n". The example assumes that "echo" will convert them into a single newline character but, for that to happen, the "-e" option needs to be included, at least nowadays. |
Michael Soyka | Mar 25, 2016 |
Other Digital Version | 52 Confirmed Errata |
The confirmed errata for page 52 says that the option to commit all files is -A, with a capital A. However, the book is correct: it should be a lowercase -a. Perhaps you were thinking of git add, which uses capital -A to add all files (which is an annoying inconsistency, especially as neither git commit -A nor git add -a are used so there's no reason for the options to differ). |
Kristofer Nelson | Sep 27, 2013 |
Page 54 code examples |
Using epub, but referencing PDF. |
Sam Gechter | Mar 27, 2014 | |
Printed | Page 55 trap paragraph |
On page 48, a "tracked" file is defined as one already in the repository or currently staged. On page 54, it says that "git rm" removes a file from both the repository and working directory. Then, two paragraphs later, it says that the command does not remove a file from the repository. This sounds like a contradiction. |
Paul C. Anagnostopoulos | Aug 24, 2013 |
Page 56 Entire top half of page |
The two code examples on that page seem unconnected. This section seems to be talking about officially removing files with "git rm", which is fine. And if one officially removes a file called "data", then the first example, trying to add it back with |
Robert P. J. Day | Sep 18, 2015 | |
Printed, PDF, ePub, Mobi, , Other Digital Version | Page 62 fig 5-4 |
I may be wrong but I think Figure 5-4 on page 62 is inaccurate. The latest tree node (the triangle on the right) in the object store is pointing to the wrong file. It's pointing to "foo" while it should have been pointing to "quux". |
Anonymous | Jul 22, 2013 |
Printed | Page 65 paragraphs 3 and 6 |
The third paragraph on page 65 says that Git compares the index to the current commit and creates new blobs for files that have changed. I don't believe this is true. Blobs are created when you perform add commands and the like, not when you commit. All commit does is create a tree object from the index and a corresponding commit object. (commit -a does create blobs, but that is irrelevant.) |
Paul C. Anagnostopoulos | Aug 25, 2013 |
Page 68 2nd. paragraph of "refs and symrefs" section |
It is read: |
Alejandro Hdez. Angeles | Dec 17, 2014 | |
Printed | Page 79 . |
On page 79, there is the phrase "The range M~12..M~10 represents two commits, the 11th and 10th oldest commits, ...", and the word "oldest" should be "newest". |
Anonymous | Feb 20, 2015 |
Printed, PDF | Page 81 United States |
Text the says Figure 6-13 'topic' "started as a branch of master but Figure 6-13 shows the commit 'A' on the 'topic' branch existing before commit 'B' |
Wayne Stidolph | Dec 07, 2013 |
Page 117 3rd paragraph |
It is read: |
Alejandro Hdez. Angeles | Dec 18, 2014 | |
Printed | Page 123 2nd paragraph (begins with "Here") |
"one commit behind the current head" is mistaken, because the current head *is* alternate, as we just checked it out; the phrase should be instead "one commit behind the master" or "one commit behind previous head". |
Enrico Maria De Angelis | Apr 10, 2022 |
Printed | Page 124 First line |
There is a extra "what" in the sentence "You can use another commit graph viewing tool, a part of git log, to see what what's been done" |
Anonymous | Feb 12, 2017 |
Page 127 The template message Git places in the text editor |
Conflicts: |
Anonymous | Feb 13, 2017 | |
Printed | Page 157 Examoke near bottom of page |
The git command "rev-parse" is used to display a sha. I believe that this command had not been used in the book prior to this. When I looked up the command, the description does not suggest to me that "rev-parse" would be the logical command for this purpose. |
Michael Soyka | Apr 13, 2016 |
Printed | Page 163 2nd paragraph |
It says that the command: |
Ross Osborn | Jan 24, 2019 |
Printed | Page 166 Botton third |
The authors write "With an amendment, anyone can see that the original commit has been modified and that it replaces the existing commit." This statement is apparently contradicted by Figures 10-10 and 10-11 on page 167. In those Figures, commit "C" has been amended to be commit "C'" and "C" is not shown in Figure 10-11. |
Michael Soyka | Apr 17, 2016 |
Page 188 third-to-last paragraph of (printed) page 188 in pdf format |
In the middle of (printed) page 188 in the pdf format, the following paragraph starts out fine, but I'm confused about the second sentence which contains "...tracking branchtracking branches...". |
Kenneth A. Wolcott | Nov 19, 2013 | |
Printed | Page 206 last line |
The name of the bare repository in the example is not consistent with example in the previous section. Should it end with "/public_html.git" rather than "/public_html"? |
MattWette | Dec 18, 2013 |
Printed | Page 206 4th paragraph |
The book has the following on page 206 2nd Ed near the top: |
Anonymous | Feb 21, 2015 |
Printed | Page 209 subsection "pushing your changes" |
This comment is a suggested improvement. |
Michael Soyka | May 30, 2016 |
Printed | Page 212 3rd paragraph |
In the section 'Getting Repository Updates' there is a line that states "Let's assume you did this after getting Bob's latest changes" (Bob changed the fuzzy.txt file). I've been following the examples but there was no command example given in the book on how to properly pull Bob's change to fuzzy.txt into the 'public_html' repo. I tried the command 'git pull', but this did not bring don the change to fuzzy.txt to my working dir and I got the following from this command: |
Anonymous | Feb 23, 2015 |
Printed | Page 223 2nd paragraph |
> The git stash push command will save your current index (when you supply the --staged flag) and working directory stateā¦ |
Christoph Lupprich | Feb 23, 2023 |
Printed | Page 224 figure 12-7 |
In figure 12-7, the commit graph for "Origin" appears to show a branch being created and then merged into "master" even though there is only one branch on "Origin". There is no such confusion in the "Yours" repository because there are two branches: master and origin/master. |
Michael Soyka | May 30, 2016 |
Page 300 Footnote #4 |
The protocol in footnote should change from git://git.kernel.org/pub/scm/git/git.git to http://git.kernel.org/pub/scm/git/git.git |
Chaz Ubell | Dec 19, 2014 | |
Printed, PDF | Page 360 3rd paragraph |
The "too" in the first sentence of the third paragraph should be "to": |
admoman | Jun 28, 2013 |