Archie Cobbs <email@example.com> writes:
> 2. Conversion from CVS -> SVN. There are some reasonable tools out
> there, but it's not clear exactly how they work, or how/if they
> handle vendor branches, etc. What exists today is insufficient for
> a project like FreeBSD where prior history is dear and loss of such
> is unacceptable.
What makes you think current tools (such as cvs2svn) lose any history?
Having it be clear exactly how they work is another matter.
Conversion from CVS to SVN is inherently complex; to make it clear how
a conversion works means describing something very complex. Certainly
cvs2svn could be better documented (I don't know about the other
converters), but it sounds like you're wishing for simplicity where
none can ever be.
> (+) It has a "theory of operation" behind it. This "theory of operation"
> is complete and fully documented, so that someone can predict
> deterministically exactly how any CVS repository will be converted.
cvs2svn.py has this (modulo bugs). Of course, to make the prediction,
you have to essentially do the same logic cvs2svn does.
> (+) Fully parameterizable. E.g., if we consider all CVS commits that
> happened within 5 seconds of each other that have the same commit
> message as part of a single SVN commit, then the "5 seconds" should
> be paramaterizable via command line flags.
We need to add that.
> (+) Configurable ability to map vendor branches into a local or
> global subdirectory, etc. (How would this work exactly?)
Your parenthetical question is the heart of the matter.
> (+) Configurable ability to map labeled CVS branches and tags into
> user-defined subtrees, etc. (How would this work exactly?)
> (+) Support for recognizing "repo copies". Often in FreeBSD a file
> is moved, but the history is preserved by copying the actual RCS
> file and changing all "FOOTAG" tags to "old-FOOTAG". The converter
> should have the ability to hunt down all such files (at the cost of
> slower operation).
That would be great. Not sure how to do recognize repository hackage
like that w/ acceptable performance.
Your converter wish list is great, I just think it's asking for the
moon :-). The problem is very, very, very, very, very hard. Just to
get it to work "correctly" at all is hard. Any enhancement beyond
that would need extremely exact description...
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Fri Jun 11 20:41:23 2004