This work is licensed under the Creative Commons Attribution License.
To view a copy of this license, visit or send a letter to Creative Commons, 559 Nathan Abbott Way, Stanford, California 94305, USA. But it's a lot easier to make up imaginary Frequently Asked Questions than it is to discover the real ones.
But CVS was not without its flaws, and simply fixing those flaws promised to be an enormous effort. Subversion was designed to be a successor to CVS, and its originators set out to win the hearts of CVS users in two ways—by creating an open source system with a design (and version control system.
We have made every attempt to be thorough in our coverage.
It is the direct result of the authors' encounters with users.
It began with Ben Collins-Sussman's observation that people were asking the same basic questions over and over on the Subversion mailing lists: what are the standard workflows to use with Subversion?
Of course, no one can promise that this book will answer every question you have about Subversion.
Sometimes the precision with which it anticipates your questions will seem eerily telepathic; yet occasionally, you will stumble into a hole in the community's knowledge and come away empty-handed.
Subversion was already in the hands of thousands of early adopters, and those users were giving tons of feedback, not only about Subversion, but also about its existing documentation.
During the entire time they wrote this book, Ben, Mike, and Brian haunted the Subversion mailing lists and chat rooms incessantly, carefully noting the problems users were having in real-life situations.
However, Subversion has a thriving and energetic development community, so already a number of features and improvements are planned for future versions that may change some of the commands and specific notes in this book. That is, Subversion manages files and directories, and the changes made to them, over time.
This allows you to recover older versions of your data or examine the history of how your data changed.
There's the overview, the obligatory guided tour, the chapter on administrative configuration, some advanced topics, and of course, a command reference and troubleshooting guide.