cvs2svn migration: making cvs branch as svn trunk while migration
ravi <[email protected]>
| Newsgroups | gmane.comp.version-control.subversion.cvs2svn.user |
|---|---|
| Message-ID | <[email protected]> |
Hello All, I am Ravi working on a email systems. Right now we release based on branch and our cvs head needs lot of clean up to make it look like production. so we wanted to migrate to svn and make the current release branch as trunk on svn and do not need to migrate any other tags, branches. we used the following command to create the dump file cvs2svn --fallback-encoding=ascii --exclude='^test-email-core-br' --force-branch=build-ready --dumpfile emailcore.svndump email my expectations are 1) want to see cvs branch called test-email-core-br as trunk on svn and will not see any other tags/branches 2) there is branch and tag with the same name (as build-ready) so used --force-branch=build-ready to force tool to treat that as branch. This is just to eliminate the validation error for ambiguity but whe we see this module in svn , i see lot of tags got migrated. dont see any recent files (latest file on svn is 3 years old). Trunk is neither any cvs branch or cvs head. Could anybody suggest me how to do this correctly? Cleaning head on cvs is not an option because of many reasons. Ravi MAV ------------------------------------------------------ http://cvs2svn.tigris.org/ds/viewMessage.do?dsForumId=1670&dsMessageId=2616040 To unsubscribe from this discussion, e-mail: [[email protected]].