Converting From CVS to SVN

| No Comments

At work, we recently “upgraded” from using CVS for all our source control to using Subversion. Subversion is what all the cool kids are using, but we chose it for several reasons, not the least of which being intelligent tag and branch management. With CVS, managing our release branches was becoming more and more hairy, while creating a new branch with Subversion is almost trivial. Other bennies:

  • Subversion runs over http, making browsing the repository incredibly easy, if a bit spare.
  • Versioned meta data called Properties
  • Subversion uses a property called externals to identify that a module should include checkouts from other modules. This means that Our main portal app can automaticlly checkout each application from the repositry in the correct location without us having to checkout the portal, then cheack out each app into the portal directory.
  • The optimized update/commit code uses diffs in both directions, making updates fast and compares almost instantaneous.
  • svn commands are sensble, easy to learn, and based on CVS commands where appropriate
  • Version Control With Subversion

Leave a comment

R.E.M. Says:

About this Entry

This page contains a single entry by Steve published on March 9, 2005 5:43 PM.

SiteLight: In The Trenches was the previous entry in this blog.

PodCastHelper 0.2 is the next entry in this blog.

Find recent content on the main index or look in the archives to find all content.

OpenID accepted here Learn more about OpenID