|
Yeah, they default to git cvsimport,
unless there are problems. Personally, I would recommend
everybody to use the cvs2git method instead. Due to the problems
mentioned by Konstantine.
The cvsimport is only really good if you have a CVS repository
that is fairly small and doesn't have a large amount of history.
It is also the only option you have if you don't have direct
access to the CVS repository as cvs2git requires direct access to
the repository. It won't work over a remote connection.
Dave
On 08/01/2012 12:11 PM, Neil Hauge wrote:
Thanks for the additional info on repo tweaking David.
We are following this general process but my email didn't make
that very clear. The webmasters are doing all of the migrating,
but unfortunately it appears that they are using git -cvsimport as
the default migration tool.
Neil
On 8/1/2012 11:51 AM, David Carver wrote:
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
_______________________________________________
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
|
