There is a quick way to generate a list of authors from a bash shell for your CVS projects. The Eclipse Foundation requires that we use "Name" &lt;committer.id&gt; or "committer.id" &lt;committer.id&gt; as the authors for the conversion, unless that committer has specifically allowed his committer email to be used.

There is a quick way to generate a list of authors from a bash shell for your CVS projects. The Eclipse Foundation requires that we use "Name" &lt;committer.id&gt; or "committer.id" &lt;committer.id&gt; as the authors for the conversion, unless that committer has specifically allowed his committer email to be used.

+

+

=== Fixing Delete-only tags ===

+

+

For most tags used in build cvs2git generates "delete-only" commits, because we only tag projects that changed it feels it has to remove all of the other ones. It makes our history look like a little fir tree.

+

+

There are scripts that can fix them (in Platform UI, it fixed ~1700 out of 2200 tags).

+

+

=== Fixing a Delete-only commit at the base of a branch ===

+

+

If you have a small branch that you didn't pre-condition the base of the branch will have a delete-only commit. To remove it in git, you have to rebase the delete-only commit onto its parent. rebase doesn't come with a move tag option, so you will have to save the tags from before and after, and move them manually to the new commits created by the rebase. I only had one small branch effecting one project that this mattered for.

+

+

=== adding a .gitignore ===

+

+

You only need one at the base of your repo. Ideally, it should look like it was there from the beginning. There might be a way to insert a .gitignore,v file into CVS before the conversion to get it there, but after the conversion you can use git filter-branch to make it look like .gitignore has been there from the beginning. This should be the last step before your publish your repo, as it re-writes every commit currently in git.

=Recipe for test conversion for p2 =

=Recipe for test conversion for p2 =

Latest revision as of 10:48, 21 July 2011

This is a modified version of the steps described by the CDT team in bug bug 316208

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. Just copy the projects to where you would like them to show up.

Running the tool

The options file for running the tool needs 2 things.

the root of the temporary CVS repo you created

the list of authors

There is a quick way to generate a list of authors from a bash shell for your CVS projects. The Eclipse Foundation requires that we use "Name" <committer.id> or "committer.id" <committer.id> as the authors for the conversion, unless that committer has specifically allowed his committer email to be used.

Fixing Delete-only tags

For most tags used in build cvs2git generates "delete-only" commits, because we only tag projects that changed it feels it has to remove all of the other ones. It makes our history look like a little fir tree.

There are scripts that can fix them (in Platform UI, it fixed ~1700 out of 2200 tags).

Fixing a Delete-only commit at the base of a branch

If you have a small branch that you didn't pre-condition the base of the branch will have a delete-only commit. To remove it in git, you have to rebase the delete-only commit onto its parent. rebase doesn't come with a move tag option, so you will have to save the tags from before and after, and move them manually to the new commits created by the rebase. I only had one small branch effecting one project that this mattered for.

adding a .gitignore

You only need one at the base of your repo. Ideally, it should look like it was there from the beginning. There might be a way to insert a .gitignore,v file into CVS before the conversion to get it there, but after the conversion you can use git filter-branch to make it look like .gitignore has been there from the beginning. This should be the last step before your publish your repo, as it re-writes every commit currently in git.

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