sirkitree.net //say it out loud, [sur-ki-tree]

There's been a lot of debate on d.o in the past about revision control - cvs vs. svn. While drupal.org is still under cvs control, there are a lot of developers using subversion as a means of maintaining their code base. So how do you deal with this when you're familiar with subversion but cvs is the preferred system to work directly with Drupal and it's contributed modules? The answer: a combination of both systems.

I wanted to outline the steps I use to do this, but came across an article today that does the job perfectly and instead of wasting cycles I'll reference you there, as it's like the author pulled this right out of my head. See http://nicksergeant.com/blog/2007/12/19/painless-drupal-revision-control... for more.