Mirror repository's start-commit hook script 173 6.1 . A sample configuration for anonymous access 203 6.3. " Rather, people asked highly specific questions, such as "How can we change the calendar- ing system to send reminders two days in advance instead of one? But it's a lot easier to make up imaginary Frequently Asked Questions than it is to discover the real ones.
Merge-tracking gatekeeper start-commit hook script 131 5.1. Mirror repository's pre-revprop-change hook script 172 5.3. No one ever called the tech support line and asked, "How can we maximize productivity?
A sample configuration for mixed authenticated/ anonymous access 204 6.5. It calls for the patient, observant attitude of a field naturalist.
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 "look and feel") similar to CVS, and by attempting to avoid most of CVS's noticeable flaws.
While the result wasn't— and isn't— the next great evolution in version control design, Subversion is very powerful, very usable, and very flexible .
Perhaps you've seen the type before: Q: How can I use Glorbosoft XYZ to maximize team productivity?
A bad Frequently Asked Questions (FAQ) sheet is one that is composed not of the questions people actually ask, but of the ques- tions the FAQ's author wishes people would ask.
Advanced Topics 49 Revision Specifiers 49 Revision Keywords 49 Revision Dates 50 IV Version Control with Subversion Peg and Operative Revisions 51 Properties 55 Why Propertie s? When O'Reilly decided to publish a full-length Subversion book, the path of least resistance was obvious: just expand the Subversion handbook.
56 Manipulating Properties 57 Properties and the Subversion Workflow 60 Automatic Property Setting 62 File Portability 63 File Content Type 63 File Executability 64 End-of -Line Character Sequences 65 Ignoring Unversioned Items 66 Keyword Substitution 69 Sparse Directories 72 Locking 77 Creating Locks 78 Discovering Locks 80 Breaking and Stealing Locks 81 Lock Communication 83 Externals Definitions 84 Changelists 90 Creating and Modifying Changelists 90 Changelists As Operation Filters 92 Changelist Limitations 94 Network Model 94 Requests and Responses 94 Client Credentials 95 Summary 97 4. 99 Using Branches 99 Creating a Branch 101 Working with Your Branch 102 The Key Concepts Behind Branching 105 Basic Merging 105 Changesets 105 Keeping a Branch in Sync 106 Reintegrating a Branch Ill Mergeinfo and Previews 113 Undoing Changes 116 Resurrecting Deleted Items 117 Advanced Merging 119 Cherrypicking 119 Merge Syntax: Full Disclosure 121 Merges Without Mergeinfo 122 More on Merge Conflicts 123 Blocking Changes 125 Keeping a Reintegrated Branch Alive 126 Merge-Sensitive Logs and Annotations 127 Noticing or Ignoring Ancestry 129 Merges and Moves 130 Blocking Merge-Unaware Clients 130 The Final Word on Merge Tracking 131 Traversing Branches 132 Tags 134 Creating a Simple Tag 134 Creating a Complex Tag 134 Branch Maintenance 135 Repository Layout 135 v Version Control with Subversion Data Lifetimes 136 Common Branching Patterns 137 Release Branches 137 Feature Branches 138 Vendor Branches 138 General Vendor Branch Management Procedure 139 svn_load_141 To Branch or Not to Branch? Repository Administration 145 The Subversion Repository, Defined 145 Strategies for Repository Deployment 146 Planning Your Repository Organization 146 Deciding Where and How to Host Your Repository 148 Choosing a Data Store 149 Creating and Configuring Your Repository 152 Creating the Repository 152 Implementing Repository Hooks 153 Berkeley DB Configuration 154 FSFS Configuration 154 Repository Maintenance 155 An Administrator's Toolkit 155 Commit Log Message Correction 159 Managing Disk Space 159 Berkeley DB Recovery 163 Migrating Repository Data Elsewhere 164 Filtering Repository History 168 Repository Replication 171 Repository Backup 178 Managing Repository UUIDs 179 Moving and Removing Repositories 180 Summary 181 6. The three coauthors of the new book were thus presented with an unusual opportunity.
It fit the collaborative nature of the open source world very well.
CVS and its semi-chaotic development model have since become cornerstones of open source culture.
Embedding Subversion 240 Layered Library Design 240 Repository Layer 241 Repository Access Layer 244 Client Layer 245 Using the APIs 246 The Apache Portable Runtime Library 246 Functions and Batons 247 URL and Path Requirements 247 Using Languages Other Than C and C 247 Code Samples 248 Summary 254 9. 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.
Subversion Complete Reference 255 svn— Subversion Command-Line Client 255 svn Options 255 svn Subcommands 262 svnadmin— Subversion Repository Administration 339 svnadmin Options 339 svnadmin Subcommands 340 svnlook— Subversion Repository Examination 363 svnlook Options 363 svnlook Subcommands 365 svnsync — Subversion Repository Mirroring 385 svnsync Options 385 svnsync Subcommands 387 svnrdump— Remote Subversion Repository Data Migration 395 svnrdump Options 395 svnrdump Subcommands 396 svnserve— Custom Subversion Server 399 svnserve Options 400 svndumpfilter— Subversion History Filtering 40 1 svndumpfilter Options 401 svndumpfilter Subcommands 402 svn version— Subversion Working Copy Version Info 407 mod_dav_svn— Subversion Apache HTTP Server Module 409 mod_authz_svn — Subversion Apache HTTP Authorization Module 412 Subversion Properties 413 Versioned Properties 413 Unversioned Properties 414 Repository Hooks 415 A. 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 .
Version Control with Subversion Community Edition Ben Collins-Sussman, Brian W. Michael Pilato Version Control with Subversion For Subversion 1.7 (Compiled from r5040) Ben Collins-Sussman Brian W. Michael Pilato Version Control with Subversion: For Subversion 1.7: (Compiled from r5040) by Ben Collins-Sussman, Brian W. Michael Pilato Copyright © 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 201 1 Ben Collins-Sussman, Brian W. Michael Pilato This work is licensed under the Creative Commons Attribution License. Org/licenses/by/2.0/ or send a letter to Creative Commons, 559 Nathan Abbott Way, Stanford, California 94305, USA. It is the direct result of the au- thors' encounters with users.