Version Control with Subversion: Next Generation Open Source Version Control

While a beginner, I have been programming for a little while now and the time came for me to put my code into a repository. I was dreading it."version control with subversion" gently and quickly took me into using Subversion. I needed to read the first few chapters twice, after that I downloaded and installed the code, and viola, my code is version controlled with minimal effort.Subversion linked readily with my IDE, Netbeans, although subversion with different IDEs is not really covered in this book.Thanks to this book, I did not have take my mind of my main project for long.I read the rest of the book (skim reading some sections) and it provides clear instructions on other possibilities, and how to set up more complex and tailored systems.A good read, presenting good knowledge, and good instruction.My evidence is that I am now using Subversion well, whereas two weeks ago I had no clue.

This book is both an excellent way to learn Subversion from scratch and an invaluable reference guide to experienced users. The material in this book is on par with (and often better than) the material available in corporate "live, instructor-led" training courses. This book covers everything from the high-level, conceptual view of Subversion to command-line usage details to the low-level internal workings of the Subversion code. Best of all, the book is easy to read and the authors use just the right amount of diagrams and flow charts (enough to clear up any questions, but not so many as to be overwhelming or distracting). I can't imagine working on a Subversion-powered project without this book. Highly recommended

I have been using CVS and SVN for more than 10 years. The enhanced merge feature in SVN 1.5 is a much needed capability. This book does a good job of describing branching and merging, what is really happening in SVN, and how to use SVN properly to meet our branching needs. That said, if you are doing multi-site, mostly independent multi-developer software development and haven't implemented a SCM system, I suggest you use GIT.

Great learning and reference book. I moved from CVS to SVN, and this book was the best resource I could find to first learn from, then use as a reference for syntax and features. This THE book for SVN.

Although I had used other code repositories in the past, such as CVS and GIT, I needed to Subversion quickly for a new job. This book is organized to accomplish exactly what I needed. It starts with comparing the basic commands to other types of code repositories. More complex topics about how Subversion works are reserved for later chapters. This is an excellent guide to Subversion.

Lots of information but I still struggle with configuration. If you are a user of svn or setting up a client this is a good book.

Essential book when I was getting up to speed. But somewhat confusing about merging and branching details.

spend too much effort on the history of CVS and SVN, which I would expected more discussion on the implementation and integration with modern development tools like Elipse and Maven

The book provided everything I needed to get my own repo up and running. I developon a MAC for IOS and Android and have seperate developments for multiple platformsusing Eclipse and Java. All the IDE's have integrated support for subversion and theyall work with my repo. Anyone should be able to get what they need from subversion with this text.

Helped me understand a couple of things while working in a svn installation. good book, it's also available online for free but it is definitely good to keep it in your phone or tablet.

I read "Pragmatic Version Control: Using Subversion" before reading "Version Control with Subversion". For most people, I would say that is the correct order in which to approach these two books. The Pragmatic book is much more readable, but "Version Control with Subversion" goes into greater depth, answering some of the questions that the Pragmatic book doesn't. It still contains tutorial material, but also feels like a more authoritative reference.Most developers think reading about version control is a waste of their time (surely they should be reading about C# or Python or the latest webby thing instead?). I disagree with that - there is little point developing fantastic code if you then lose your greatest work because version control isn't being used correctly. However, I am also realistic about how much time most developers can be persuaded to spend reading about subjects such as version control. Therefore, I would suggest that most developers on a team using Subversion should read the Pragmatic book, as that will give them enough detail to do what they need to, but without being too long or being heavy to read. However, I think it is worth a couple of developers at each site spending the extra time required to also read "Version Control with Subversion" in order to sort out the organisation and practices to follow at that site, including development of any scripts that might be required to support those practices. "Version Control with Subversion" gives extra detail about the differences between version 1.4 and 1.5 of Subversion, more detail on the pros and cons of using properties, use of externals etc. Most developers don't need to know these things, but a few do.So, a good book, a bit heavier to read than the Pragmatic book, but still worth the effort for those developers who need to get involved in version control a bit more deeply.

Wir nutzen nur einfache Funktionen von Subversion, die Einrichtung eines Subversion-Servers klappte ohne Probleme. Auf meine Fragen bzgl.: Distribution von Dateien, Programmcode-Versionierung und einfache Merge-Aktionen bekam ich ausreichende Antworten. Mehr nutze ich nicht, unsere Programmierprofis tendieren eh mehr zu Git. Insofern ist SubVersion wohl eh ein Auslaufmodell.Wir verwalten und archivieren Bilder, ca. 100kB bis 1MB pro Bild. Auch nach vielen tausenden Bildern läuft SubVersion stabil und schnell. Dafür ist es vielleicht besser geeignet als Git?!

The book was packaged decently, arrived within the expected time. The condition of the book was as advertised ("good"), no stains scratches or smudges.