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.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.Of course, no one can promise that this book will answer every question you have about Subversion.
What I love about this book is that it grew out of just such a process, and shows it on every page.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.In this regard, many people think of a version control system as a sort of Subversion can operate across networks, which allows it to be used by people on different computers.At some level, the ability for various people to modify and manage the same set of data from their respective locations fosters collaboration.When this happens, the best thing you can do is email and present your problem.The authors are still there and still watching, and the authors include not just the three listed on the cover, but many others who contributed corrections and original material.When O'Reilly decided to publish a full-length Subversion book, the path of least resistance was obvious: just expand the Subversion handbook.The three coauthors of the new book were thus presented with an unusual opportunity.Do branches and tags work the same way as in other version control systems? Frustrated at seeing the same questions day after day, Ben worked intensely over a month in the summer of 2002 to write , a 60-page manual that covered all the basics of using Subversion.The manual made no pretense of being complete, but it was distributed with Subversion and got users over that initial hump in the learning curve.