Quote:
Originally Posted by
cbkihong
However, if I have not misinterpreted the documentation for cvs2svn, that does not appear to have an option for migrating a CVS branch only. My understanding is in CVS, unlike in SVN that a branch is a copy and just works like the trunk except on a separate tree, CVS branches are rooted with a revision on the parent branch and it will not be very surprising to me if indeed cvs2svn does not support migrating a branch only directly.
Correct me if I am wrong.
I guess the original poster already knows about cvs2svn because that is mostly the way to convert a CVS repo to SVN ....
Yes I do know about cvs2svn.
First of all it turns out that the person which requires the SVN conversion is marketing director. So we reviewed what he NEEDS exacty and ...
We solved the problem in not very sciantific way ...
Here is how:
1. I copied one part of the things that we need to cvsroot/tmp/svn directory
then used simple bash script with cp and cvs rtag commands to delete all unnecessery branches and tags .. (I got the branches / tags from cvsweb interface)
2. copied second part, and repeated 1, then tirth part ... and so on ...
3. After long time of copy / cvs rtag -d (allmost 24h ).... we had one not very big (approx. 1G) repository in cvsroot/tmp/svn.
This repository was compressed, and sent to my colege, for SVN transformation on remote server.
My personal conclusion:
Before proceed, make sure you know that the person that wants huge changes to well working (and proven) system knows what he / she wants
)
Cheers.