i'm currently considering testing svn as a replacement for our cvs repository. The first
impression of svn is very good, because the main problems of cvs are solved, as they are:
- slow checkins
- sloooow tagging
- tagging only allowed for thos files with write access, not through the whole repo
- slow WAN access
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.
May it be ok to split the repository into several and convert it on several computers?
But then a commits may be splitted into two. Can we import the several dumps? Or is this
not possible because the revisionnumber is shared among the whole repo?
(Example: the repository path java/* is converted at comp1 and www/* is converted at comp2
If java was commited on 1/1/00 and 1/3/00 and gets the number 4711 and 4712. If something in
www/* was committed on 1/2/00 it should get the number 4711.5? Or can the revision numbers
be corrected during importing? Or can we only distribute cvs2svn-pass4 [i believe] over
- Is a svn2cvs planned?
This is not that we want to step back to cvs, but in my opinion is cvs/rcs a well tested
and robust format. If we step forward to another versioning system, it may only import
- 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?
- 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 ;-)
- Can you put in a Issue about conversion of branches? I havent not enough rights...
So I may follow the current development process. Alternatively, when may the branch import be
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
Apart from this little problems I'm very interrested in testing and maybe using svn, especially with this
Freiberger Str. 39
phone: +49 (0) 351 43958 214
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Tue Jun 17 20:15:53 2003