Jan Mönnich <Jan.Moennich@newtron.net> writes:
> Now I'm running a test conversion of our repository with cvs2svn and
> there are some questions,
> which I havent found in the FAQs or issues:
> - Its terrible slow. it runs since 20 hours and commits currently
> the 20 march 2001, 2 years to go...
> (aktuell revision 8800)
> The problem is, that I havent only two days to convert the
> repository (saturday and sunday) otherwise nobody is able to
> develop something.
I'm surprised it's that slow! Do you know appx how many file changes
per revision there are?
One solution: you can keep track of all commits that came in since you
started the conversion (just put some trivial script into
CVSROOT/loginfo to record the path and the new revision number). Then
after the conversion is done, you can go get all those commits and
replay them into the Subversion repository manually, or just mail the
relevant developers and point out to them that the change may not have
been ported over...
> - Is a svn2cvs planned?
Not as far as I know.
> - While importing, I see always a "trunk" directory.
> In our repo we have the directories java/tools/*, java/framework/*, java/newtron/*
> and www/framework/* www/newtron/*
> And now its importing java/trunk/newtron/* java/trunk/framework and so on?
cvs2svn by default uses the
plan that we recommend in the book. Currently, it just uses the
top-level directories in the CVS repository as the project roots, but
it may stop doing that, thanks to a recent thread about how a --prefix
argument would be more useful.
> - I've three corrupted ,v-files . Is there a tool to repair them
> (maybe with little loss of history). cvs2svn crashes in pass1, but
> cvs crashes too if we are checking out a very old version. (I can
> send you this files, if needed or only interested ;-)
I don't know if there is a tool -- if there is, we certainly don't
ship it with Subversion. Maybe they can be repaired by hand?
> - Can you put in a Issue about conversion of branches? I havent not
> enough rights...
There's no need for an issue -- branch conversion is all I'm working
on right now :-).
> So I may follow the current development process. Alternatively,
> when may the branch import be
> completed (approximately)
> Should it be possible to import the branches later?
> Aehm, here are some facts about our repository:
> - contains the history from november '99 to today
> - 51000 files, several projects with shared code
> - ca. 150 Branches
> - 1,2 GB
Thanks for the reports; I hope you'll keep trying cvs2svn.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Tue Jun 17 21:30:50 2003