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 |
| Printed |
Page 22
1st paragraph |
Good book. Two minor things.
* I don't think the concept of _working tree_ is defined properly (if at all). I'm using the printed version of the book, so I may have overlooked it.
* You may want to consider adding _working tree_ to the index.
|
Anonymous |
Dec 19, 2018 |
| Printed |
Page 50
5th paragraph |
My understanding (and testing) supports an alternative explanation (note three commands, not two):
"
This is actually just a shortcut for renaming the working file outside Git, then using <tt>git add</tt> on the new name and <tt>git rm</tt> on the old name:
<tt>
$ mv foo bar
$ git add bar
$ git rm foo
</tt>
"
Apoligies if I got it wrong, please let me know either way. Thanks - very good book.
|
Giulio Agostini |
Jun 12, 2016 |
| PDF |
Page 116
Second paragraph |
"A simple ref points directly to an object ID. Git follows a symbolic ref such as "master" until it finds a simple ref; for example, HEAD points to master if you are [on] that branch, and master points to the commit at the branch tip."
I thought that "master" (or any branch name) was a *simple* ref since it referred directly to a commit, and that HEAD was considered a symbolic ref since its value changes depending on which branch you're on. Take a look at how you define refs back on p 17 -- wouldn't a branch name be considered a simple ref under those definitions? Or am I misreading?
Oh, and two other typos on that page. First, missing word "on" in that very paragraph I quoted. Also, in point 1. further down, should "HEAD" not be rendered in monospaced font as is "MERGE_HEAD" and "FETCH_HEAD"?
|
RobDay |
Jun 18, 2015 |
| Printed |
Page 210,214
Index-D, Index-R |
L.S.
i'm new to Git and I tried to start putting in repo's and working with it and expecting this book to be helpfull with this. But it did not (that much).
Instead I used Michael Hartl's 'Ruby on Rails tutorial' chapter 1.4.
And I used Google to help me to find a solution for deleting/removing a repository that was empty.
My complaints/remarks are:
1-put in one or more examples of the most common usage of GIT.
2-put in more usable keywords in the index (so: delete a repository/remove a repository)
There may come more suggestions from my side because I'm not yet ready studying and overall using of Git.
regards, Barry Jobsis
|
B.Jobsis |
Dec 08, 2017 |