Version Control with Subversion [Paperback]

This first edition has numerous code errors in examples, and basic command listings. It is a total waste of time and money trudging through misprints. This book is 1month old and is already useless. For example if you followed the instructions in Chapter 2 as to how to create a repository, then followed the instructions on how to checkout you would Fail right away because the example command is missing a "/".... Small but high impact misprint!

If you're serious about stepping up to subversion, this book is licensed under GPL and as such can be downloaded for free from svnbook.red-bean.com.

My only regret with subversion so far is spending $25 to find out I could have gotten a much more error free version for nothing!

If you are a CVS user, you need to immediately move to Subversion. CVS is damaged goods (no atomic commits, broken tags/branches, broken client/server, etc..). Subversion fixes all of this and takes it a generation further (WebDAV access, sensible branching, excellent diff'ing, etc).

This book does an excellent job of teaching the reader exactly how to effectively use Subversion. Whether new to revision control, coming from CVS or from some other RC system, the Subversion Book provides a very clear and often humorous guide to effectively deploying, administrating and using Subversion.

An excellent book.

This book is an excellent resource for novice and experienced Subversion users alike. The first two chapters provide background on why subversion came into existence and general version control concepts. Anybody new to Subversion should carefully read chapter 3. The 'Basic Work Cycle' section explains the day-to-day use of Subversion well.

Chapters 5 and 6 have been invaluable in setting up our repositories. I particularly recommend people read the section on choosing a repository layout prior to setting up their repository. Setting up a Subversion repository to be served through Apache is more complicated than a local repository, but the 'httpd' section of chapter 6 clearly covers what to do. We now have a Subversion repository served through Apache that authenticates users with client-side certificates and encrypts communications over SSL.

Chapter 7 provided the information I needed to really get Subversion working exactly as I wanted it to. I have modified my config file to set what files Subversion should ignore and also what properties to set automatically. In addition, we have set up our projects so that they all have transparent access to the company's reusable code library using the svn:externals property (covered in the externals definitions section).

Appendix A is the place to start if you are an experienced CVS user making the transition to Subversion. There are a few significant changes that you need to be aware of.

The examples in the book use the command-line client, but Appendix D (Third Party Tools) provides URLs for the many GUI clients available, if that's your preference.

Share your thoughts with other customers: Create your own review

Search Customer Reviews

Only search this product's reviews