Dave,
You may want to take a look at the thread in the Sapphire migration bug referenced below… Based on comments in the Git migration wiki and those found elsewhere on the web, I would not have expected git-cvsimport to be positioned as the standard solution, yet it was. I suspect that the policy is changing now that a number of projects have had trouble with the git-cvsimport route…
- Konstantin
From: wtp-releng-bounces@xxxxxxxxxxx [mailto:wtp-releng-bounces@xxxxxxxxxxx] On Behalf Of David Carver
Sent: Wednesday, August 01, 2012 8:52 AM
To: wtp-releng@xxxxxxxxxxx
Subject: Re: [wtp-releng] Dali Git migration
Please make sure to review the Git Migration wiki page:
http://wiki.eclipse.org/Git/Migrating_to_Git
Webmasters can run the cvs2svn scripts for you if you do not have access to the file system.
Just open a bug and ask them to run the conversion. Once converted, if you need to do any tweaking (i.e. filter out branches, commits, etc) you can use git filter-branch to accomplish cleanup on the git repository.
Dave
On 07/31/2012 01:45 PM, Neil Hauge wrote:
Thank you for this additional information. It is concerning to me that git -cvsimport is still the default migration mechanism.
Neil
On 7/31/2012 1:17 PM, Konstantin Komissarchik wrote:
For further context... A number of projects have been encountering problems
with git-cvsimport migration like ones that Neil is describing. A bit of
online research revealed that there are a number of known outstanding issues
in this tool that lead to missing commits, missing branches, corrupted
branches, etc. The cvs2git tool is the way to go as the tool is a chain of
CVS-to-SVN and SVN-to-Git, both of which are far more mature than direct
conversion using git-cvsimport.
See this for Sapphire's experience with the migration:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=374976
The way I detected issues with Sapphire migration is by comparing the tip of
each branch in CVS with the tip of each branch in migrated Git repository.
Thanks,
- Konstantin
-----Original Message-----
From: wtp-releng-bounces@xxxxxxxxxxx [mailto:wtp-releng-bounces@xxxxxxxxxxx]
On Behalf Of Neil Hauge
Sent: Tuesday, July 31, 2012 9:53 AM
To: Webtools releng discussion list
Subject: [wtp-releng] Dali Git migration
I wanted to alert other WTP projects to some of the issues we are
encountering with our git migration. We have run into inconsistencies in
some of our branches, where the file revisions aren't accurate, resulting in
compile errors. There are likely cases where these inconsistencies would
not result in compile errors, so wanted to make sure that folks take the
time to verify that the tip of a given branch matches expected contents from
CVS.
We are going to re-import our CVS contents to Git using a different
migration tool as described in our migration bug -
https://bugs.eclipse.org/bugs/show_bug.cgi?id=385628.
I will report back results after we have had a chance to verify the
migration.
Neil
_______________________________________________
wtp-releng mailing list
wtp-releng@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-releng
_______________________________________________
wtp-releng mailing list
wtp-releng@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-releng
_______________________________________________
wtp-releng mailing list
wtp-releng@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-releng
