Essential CVS

Errata for Essential CVS

Submit your own errata for this product.


The errata list is a list of errors and their corrections that were found after the product was released. If the error was corrected in a later version or reprint the date of the correction will be displayed in the column titled "Date Corrected".

The following errata were submitted by our customers and approved as valid errors by the author or editor.

Color Key: Serious Technical Mistake Minor Technical Mistake Language or formatting error Typo Question Note Update



Version Location Description Submitted By Date Submitted Date Corrected
Printed
Page 8
2nd paragraph under Installing CVS in Chapter 2

http://www.9780596004590gui.org should be http://9780596004590gui.sourceforge.net/

Anonymous   
Printed
Page 11
after su root

It is recommended to use "su - root", with the "-" so that your profile is re-read so you have the new enviroment variables. Some profiles/distro's require the - option to install things.

Anonymous   
Printed
Page 15-16
Example 2-5

The example shows creating a repository under /var/lib/9780596004590root, but thrice shows "ls -la /home" instead of "ls -ls /var/lib" ls -la /home should be: ls -ls /var/lib

Anonymous   
Printed
Page 16

Modify the paragraph: 'To allow others to use the repository, create a Unix group for CVS users and chgrp the repository root directory to that group. Set the directory's SGID bit...' To: 'To allow others to use the repository, create a Unix group for CVS users and chgrp the repository root directory to that group. Add users to that group, using the appropriate command for your system (often 'gpasswd'). Set the directory's SGID bit...'

Anonymous   
Printed
Page 17
Paragraph 1:

instead of: 'When you have created a new repository, you may want to import a project' use: 'When you have created a new repository, you may want to import your first project' After the first paragraph, add a note: 'Your repository can hold one project, or can hold many different projects. CVS scales well: a repository can help a single person with a small job to do, or can be used by a large company to provide version control to hundreds of separate groups.'

Anonymous   
Printed
Page 22
Final line on page

/var/lib/9780596004590root/example/file1,v &lt;-- file1 should be: /var/lib/9780596004590root/example/file1,v <-- file1

Anonymous   
Printed
Page 25
Line 12 of Example 2-19

/var/lib/9780596004590root/example/file3,v &lt;-- file3 should be: /var/lib/9780596004590root/example/file3,v <-- file3

Anonymous   
Printed
Page 26
Line 10 of Example 2-20

/var/lib/9780596004590root/example/file3,v &lt;-- file3 should be: /var/lib/9780596004590root/example/file3,v <-- file3

Anonymous   
Printed
Page 39
Last sentence on the page

The word "on" is missing. "It can also take files or directories as parameters and operate recursively them." should be: "It can also take files or directories as parameters and operate recursively on them."

Anonymous   
Printed
Page 40
First tip

the sentence: "Use 9780596004590 status or cvs update -n to find out which files need to be updated or committed." Should be: "Use 9780596004590 status or cvs -n update to find out which files need to be updated or committed."

Anonymous   
Printed
Page 76
Next to last line of page

"independant" should be spelled "independent"

Anonymous   
Printed
Page 102
Last 2 lines

Example 5-14 shows a diff command that compares revisions 1.2 and 1.3 of the Makefile file, with the option to display a few lines of context around each change. Should be: Example 5-14 shows a diff command that compares revisions 1.2 and 1.3 of the Makefile file, and uses the '-c' option to display a few lines of context around each change.

Anonymous   
Printed
Page 104
last paragraph

"relevent" should be spelled "relevant"

Anonymous   
Printed
Page 131-134
8 instances in Example 6-7

The master CVS lock is named "#9780596004590.lock". However in the example the wrong name "#cvslock" is consistently used.

Anonymous   
Printed
Page 171
Paragaph before example 7-10

Please add the following to the paragraph before example 7-10: (If using this code fragment outside a subroutine, replace 'return' with 'exit'.)

Anonymous   
Printed
Page 178
"T" option

"T Report on records of files being tagged or rtagged" should be: "T Report on records of files being rtagged"

Anonymous   
Printed
Page 226
Last 9 lines on page of Example 2

"Concurrent Versioning System" should be: "Concurrent Versions System"

Anonymous   
Printed
Page 275
discussion of operator

The correct spelling of the name for "^" is "caret" not "carat".

Anonymous   
Printed
Page 275
discussion of ? operator

I believe the patterns that match "fo?bar" are "fbar" and "fobar", that is, the element "o" zero or one times, not "fobar" and "foobar" as stated. In the same spirit, I think the earlier example of "fo*bar" under the discussion about the * operator would also match "fbar". I have to say that I get into trouble with the * operator about half the time I use it, so I avoid it in favor of +, which behaves more nearly as described in the book. AUTHOR: CVS uses a strange system of regular expressions, which is apparently based on Emacs REs. I just checked the code, and ? is handled identically with + in most of the source, but does not accept 0 repetitions. But I just ran an empirical test, however, which disagrees with the documentation and the book, and apparently the code. Argh. READER: Jenn's tip about emacs showed me an easy way to test my claim (I do not ordinarily use emacs, but I have it). I set up 3 data lines, like this: fbar fobar foobar I then used the emacs regular expression search to look for matches to regular expression fo?bar. I got matches at fbar and fobar, but not at foobar. This is exactly what I had predicted in my note, and it corresponds to normal regular expression behavior - nothing is broken, just normally confusing. This test regular expression can be re-written as f(o)?bar - the ? operator applies to the pattern within the escaped parentheses. This pattern is allowed to occur zero or one times. Therefore, foobar will not match. (outside back cover) Last line of first paragraph "Concurrent Version System" should be: "Concurrent Versions System"

Anonymous   
Printed
Page 282
End to para 1

"twith a Java Runtime Environment" should be "with a Java Runtime Environment"

Anonymous   
Printed
Page 284
End of para 2

"follow the procedures givin in Chapter 2." should be "follow the procedures given in Chapter 2."

Anonymous   
Printed
Page 315
Index entry for merging

merging, 92 should be: merging, 83

Anonymous   
Printed
Page 321
2nd to last paragraph, Colophon for CVS Essentials

"hybernation" should be: "hibernation"

Anonymous   
Printed
Page 321
last paragraph, Colophon for CVS Essentials

"hybernation" should be: "hibernation"

Anonymous