Migration from CVS to SVN is often described on the repository server side only. When migrating you would normally delete your CVS working copies and check out a fresh one from SVN. However in case of a live website you may not want to reinstall the entire working copy (including locally changed configuration files and unversioned files). Reinstalling the website may cost time, increase server load and cause website downtime.
To overcome this problem you can convert the working copy from a CVS working copy to an SVN working copy, by replacing the CVS meta data with SVN meta data directories in your working copy:
Continue reading "Client side migration from CVS to SVN"