From: Spiro Trikaliotis (ml-cbmhackers_at_trikaliotis.net)
Date: 2007-01-12 19:28:22
Hello,
* On Fri, Jan 12, 2007 at 05:50:10PM +0100 Ullrich von Bassewitz wrote:
> cvs2svn, as mentioned by Marko, sounds like a possible solution, and I will
> have a look at it once I have some spare time.
cvs2svn has some problems. Anyway, from my experience, it either refuses
to convert the CVS at all, in which case it aborts with a clear error
message, or everything works fine. I never experienced (or heard of)
cvs2svn reporting success, but generating a broken SVN.
One example where svn2cvs bails out (at least, it did some time ago. I
don't know if this has been fixed, never checked for this): Some people
have created a tag to denote the trunk of CVS. For example, a tag TRUNK
with is set to revision 1. This way, it was possible to go back to the
trunk without needing to use "cvs up -A", which resets all other sticky
options, too.
Now, cvs2svn refused to do the conversion with such a tag, as cvs2svn
meant that such a tag was not allowed. In fact, this is a branch tag in
the RCS sense, not in the CVS sense. So, one could argue if this was
still a valid CVS repository. Anyway, CVS is able to generate it, thus,
IMHO, it should be considered a valid one.
I know there was some discussion if this should be fixed or not. As I
told, I did follow if it was fixed.
So, to make a long story short: From my experience, if cvs2svn ends
without an error report, it did a fairly good job in the conversion. Of
course, this does not mean I would throw away the CVS repository; but
backing it up might be good.
Regards,
Spiro.
--
Spiro R. Trikaliotis http://opencbm.sf.net/
http://www.trikaliotis.net/ http://www.viceteam.org/
Message was sent through the cbm-hackers mailing list
Archive generated by hypermail pre-2.1.8.