VCP (via svk/SVN::Mirror) is pretty much state of the art.
Yes, it's slow - but incrementals after the initial hit aren't so
hideous. (Although it really does depend on the size of the
repository - it has to scan all the files to see what's changed --
that's just a fact of CVS's architecture.)
It could probably be optimized by integrating CVSdb (comes with
ViewCVS) to avoid the entire repository scan.
CVSdb could also be used to put together a cheaper conversion tool.
-R
At Wed, 12 Jan 2005 20:36:47 +0100,
Florian Weimer wrote:
>
> What's the current state of technology in unidirectional CVS mirrors
> (from CVS to Subversion only)?
>
> Unfortuantely, VCP is too slow (it's the GCC repository 8-/). I could
> do it manually, but I'd rather have some automated approach which
> honors adds/deletes. Changeset reconstruction is not strictly
> necessary. Correctness (i.e. local repository and remote CVS
> repository remain in sync) is very desirable.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jan 18 05:43:56 2005