Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
We are recently migrated from CVS to SVN and I have setup SVN WebDAV on ubuntu server converting existing cvs repo. The developers start using new version control system SVN soon. What would be the best practice to migrate from svn to cvs back if anything goes wrong?(something like committing changes also to cvs while using svn).
Thanks in advance!
There is no reliable solution that I know of to keep CVS synchronized with any other version control system. (There are some that claim to do so, but they are all very fragile.) cvs2svn does not have an incremental mode that allows you to migrate additional CVS commits that have been added since the last cvs2svn conversion. Incremental conversion of a CVS repository is technically difficult, not least because CVS has non-atomic commits, doesn’t record the dates when branches/tags were created, and allows retroactive changes to the history of a project.
Your best bet for migrating away from CVS is to do a test conversion, have your developers try it out (with the understanding that any test commits will not be retained), then choose a flag day and do a one-way migration using cvs2svn. I can hardly imagine that you will want to go back to CVS, but if you do, you don’t have much alternative but to restore a backup of the CVS repo from before the conversion.
Disclaimer: I am the cvs2svn maintainer.