Overview of the steps for platform conversion:

Precondition the CVS repo

If you have maintenance releases where your release was tagged R3_6 but only projects that were changed were branched R3_6_maintenance the cvs2git conversion tool will create a maintenance branch with only the projects that were changed in it. This makes the maintenance branch useless. But if you branch every project in your CVS repo before the conversion, you will get correct branches in git.

For each maintenance branch you care about you have to fix the branch + the tags, ex: R3_6, R3_6_1, R3_6_2, and R3_6_maintenance.

Create a temp repo

cvs2git changes the cvs repo as it goes (it reads and modifies the ,v files), so you should do your conversion on a temp repo. For a component like Platform UI, that allowed us to shape our repository from many top level CVS modules to its current shape: repo/bundles/[plugin_projects], repo/tests/[plugin_projects], etc.

Recipe for test conversion for p2

Copy the existing repository to a temp location

mkdir ~/cvs; cd ~/cvs

cp /home/data/cvs/rt/org.eclipse.equinox.p2 .

Remove broken symlinks in the repo from all to the components we moved above