Errata for Pragmatic Version Control Using Git

#35530: "Branching is so key to how Git operates there’s a full chapter explaining what they are and how to use them."

Noun-pronoun disagreement. Should instead read: "Branching is so key to how Git operates there’s a full chapter explaining what IT IS and how to use IT."--Albert Vernon

#35918: 2nd paragraph after the command snippet.

Each one marks the progression of you code.

should be

Each one marks the progression of YOUR code.

-Shant--Shant Hovsepian

#35440: Para:

We’ve got the basics—adding new files, modifying existing ones, and
looking at the repository’s history—out of the way; now let’s get into
something more meaty and tur n are attention to branches.

should end:

"turn our attentention to branches."

#35520: In second paragraph from the end of the page:
It says:
"[...] and the directory where you want *to* repository to live. [...]'
I think it must say:
"[...] and the directory where you want *the* repository to live. [...]'--Albert Oliver Serra

#36127: Near the end of the sentence immediately before the git clone command, "you can always clone the repository to get repository that I built": insert "the" between "get" and "repository."--Bruce Hobbs

#35683: At the bottom of the page it says: " .. either you one you created in the last chapter, or a cloning mine ..". Should probably be: " .. either THE one your created .."--Magnus Skog

#35758: Third para:
"Since I know that MacVim swap files always begin with a period and end with .swp, I just add .*.swp to the .gitignore and Git ignores all matching files."
Missing 'file' after '.gitignore'--James Silberbauer

#35759: First para:
"If the answer to that is yes, you need to ignore it by adding the rule the .gitignore file and committing that file to the repository."
Missing 'to' between 'rule' and 'the'.--James Silberbauer

#35885: In the sentence "If you’ve skipped ahead, you can clone the repository from it’s GitHub repository" in the last paragraph, that "it's" should instead be "its" i.e. with no apostrophe.--Nick Grimshaw

#35775: The first sentence beneath the "Straight Merging" header reads as follows: A straight merge takes one branch and merges it into the another branch.

There is an erroneous "the" -- it should read: A straight merge takes one branch and merges it into another branch.--Joseph Jaramillo

#35433: In third paragraph starting from the end of the page.
It says:
"Using the -N notation allows you to subtract out that many lines.
You can use -L 12,-2 to show lines 2 and 3 of your file."

Lines are wrong.
It must say:
"You can use -L 12,-2 to show lines 11 and 12 of your file."--Albert Oliver Serra

#35452: Para starting: "As you can see, Git displays...", change

"show us when whole files can been copied"

to

"show us when whole files have been copied"--Robert Rainthorpe

#35412: "it’s made simple by a program called Gitosis, which
we’ll cover in the (as yet) unwritten sec.gitosis."

This section is no longer unwritten...--Asgeir S. Nilsen

#35413: "Your local copy created by cloning works just like it would if you had created it yourself using git init like we talked about in the (as yet) unwritten sec.common.init,"

Guess this is referring to section 3.1?--Asgeir S. Nilsen

#35924: In the second paragraph of section 7.4, "This is the step you go through to send your commits with another repository" should read "This is the step you go through to send your commits to another repository"--Nick Grimshaw

#36168: "developer named Erin and you constantly pull changes from their repository" should be "*a* developer named Erin and you constantly pull changes from *her* repository"

#35785: Last prompt on the page:
"prompt> git checkout -b another-from-1.0"
Should this not read:
"prompt> git checkout -b another-from-1.0 1.0"?
(The para above mentions the tag name as a second parameter)--James Silberbauer

#35495: The text reads as:

You can use the command on one line
without the “\.”, those are here to make the command fit on the page.

This should probably be:

You can use the command on one line
without the “\”, those are here to make the command fit on the page.

The backslash doesn't actually have a dot.--Alex Ezell

#35496: The text reads as: You can use the command on one line without the “\.”, those are here to make the command fit on the page.

This should probably be: You can use the command on one line without the “\”. Those are here to make the command fit on the page.

In addition to my previous report of the dot problem, the original appears to be a run-on sentence as well. At the very least, it could use a semicolon.--Alex Ezell

#35929: In the second paragraph, the sentence "... on page 66 we talked about how branches are just is a pointer to the latest commit in that line" has an extraneous "is".--Nick Grimshaw

#35959: para. 7: "I shortened the commit on line the second line of the output so it would ..." should be "I shortened the commit on the second line of output ..."--russell muetzelfeldt

#35932: In the second paragraph in the sentence "First, you can try to enlist the help of a sysadmin buddy bribing, err... paying him to help your out", that final "your" should be "you".
--Nick Grimshaw