Revision Control System Recommendations

Question

I\'ve reached a point in my independent development work where I would like to start using Subversion techniques.

Up to now, I\'ve been simply making backups by exp

Answer 1

Use Git or Mercurial

---

Once upon a time, cvs almost completely replaced its competition and ruled the world of version control.

Then it was itself replaced by svn.

And now, svn has been replaced by git.

Git is more complex than svn, so an svn project might well want to just keep bashing along and not convert.

But svn's days are numbered. Git, Mercurial, and some proprietary systems are clearly the future of the VCS world. There are even mechanisms to cross-operate with other types of repositories.

Finally, the transition is easy, because git can be used with a central repo just like it was a (much) faster version of cvs or svn.