Version Control with Subversion

Errata for Version Control with Subversion

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
Page 248
4th paragraph, near middle of page

The text states the following:

'Subversion has combined the CVS P and U codes into just U. When a merge or conflict occurs, Subversion simply prints G or C, rather than a whole sentence about it. For a more detailed discussion of svn status, see "svn status" in Chapter 3.'

I can find no information in Chapter 3, or anywhere else in the book (or on the web) where there is any mention of the character 'G' pertaining to the "svn status" command, so I suspect the text is in error.

Thank you for your consideration,
Bruce Reid

Note from the Author or Editor:
You're right, 'G' is only printed by 'update' or 'merge', not by 'status'. Looks like this is already fixed in the online version of the book over at We've changed the section to say 'update' rather than 'status'.

Bruce Reid  Jul 08, 2010 
Page 212
Second last paragraph (Configuring Apache for Digest ..)

The book states that changing from Basic to Digest authentication requires minor modifications. In fact, it looks like one needs just to change the authentication type (AuthType) and to add the authentication domain (AuthDigestDomain).

This is of course not the whole truth. One needs also to setup a new authentication file using *htdigest* instead of htpasswd. The authentication file generated by htpasswd will not work.

Note from the Author or Editor:
Hi, thanks for the feedback. In the future, it's probably easier just to file a bug at I've moved this report over there:

And I've filed it as a minor clarifying enhancement, not a 'serious techincal mistake'. The book specifically says it's not a definitive reference to configuring Apache, and even implores the reader to "Be sure to consult Apache's documentation for full details."

Wolfgang H?felinger  Feb 10, 2009