Historical errata for Pragmatic Version Control using CVS

Second para: “we’re” should be “we’ve”

In Mac OSX, the Terminal application is under Applications/Utilities.

First para: “All you have to do it” should be
“All you have to do is”

The version number for Color.txt in some of the examples should
be 1.1.1.1, not 1.1. Also applies to page 129/131 under step 5.

In the body text, the work ‘cvshome’ was incorrectly set as a url,
and hence tries to link to a site called ‘cvshome’. The footnote
contains the correct url.

‘using a single method’ => ‘use a single method’

Fix spelling of Kerberos

/etc/password should be /etc/passwd

Third para: ‘chose’ should be ‘choose’. ‘is leaves you’ should be
‘it leaves you’

Last paragraph: ‘tricker’ should be ‘trickier’

at bottom of page: ‘phase’ should be ‘faze’

There’s a consistency issue with tag names: the table uses hyphens,
but the text uses underscores. Also, the table uses ‘RB’ for release
branch, while the text sometimes uses ‘BR’.

Under branch tags, it says: “When you subsequently refer to the
branch tag, it’s as if you were referring to the state of the files
at the point the branch was created.” It should say that the branch tag refers to the latest revisions on the branch.

In the second example, the line “cvs -j PRE_1234 -j
POST_1234 update” should read “cvs update -j PRE_1234
-j POST_1234”

bottom of page: change “we’ll assuming” to “we’ll assume.”

Duplicate word ‘and’ in ‘db/’ paragraph

Duplicate word ‘empty’ in footnote

Bullet 1: ‘Chose’ -> ‘Choose’

First para: “we’re been relying” -> “we’ve been relying”

Checking out the module ‘halfrubysamp’ will create a
directory also called ‘halfrubysamp’, and not
‘halfrubysamp/samples’ as stated

Missing ‘-ko’ option in import command for readline update

The -ko option in step 3 is in the wrong place. It should be “cvs import -ko …”.

Merant got bought by Serena, so the URL for PVCS (now called Professional) is www.serena.com

Footnote 1: cvshome.org is no longer maintained, and there are no binaries for Windows. Looks like development of cvs moved to savannah.nongnu.org, with source releases are available from Gnu mirrors, but no binary releases any more.

Last line on the page: ‘… that follow it’ should be ‘… that follows it’

Example at the end of page, line
CVSROOT> cd ..
should be
tmp/CVSROOT> cd ..

Example at the end of page: maybe it would be good to explain command ‘cvs release’. It is introduced here for the first time.

The next time ‘cvs release’ command is used: page 102.

5th paragraph, "…context. we

Both the URLs specified at the bottom of the page for cvsadmin & cvspadm do NOT provide the respetive tools.
i.e those links are invalid.

Through Google search found the following link for cvsadmin:
rpmfind.net/linux/RPM/PLD/dists/ra/updates/general/i686/cvsadmin-1.0.3-1.i686.html

However cvsadmin for Debian , was not found through Google search.

Best Regds
VETRI

Software Config Mgmt /
Build & Release Mgmt /
Change Mgmt Consultant - IBM-Rational & OpenSource Tools

www.Global-Software-Engineering.com

Singapore

One comment came to mind while going through Chap. 6 under “Checking
Your Workspace” on page 89. You show how to get a more abreviated
status output in the Unix shell and then suggest that Windows users may
need to install some additional tools to achieve the same result.
Actually Windows users can do the same thing without anything extra.
The following command will do the same thing.

D:\\src\\cxxi>cvs -q status | find “File:” | find /V “Up-to-date”