Re: CVS Migration

Max <max@alleged.net> writes:

> There is quite a lot of material on the project web page for me to use,
> however, I will be doing usability tests as well, including attempting
> to transition an existing complex CVS repository.

As the front page says -- read the FAQ, the Subversion Handbook, and
perhaps even the Design document.

> Is there currently a tool to port a repository from CVS? Exporting a
> repository and importing it into svn would be straightforward, but all
> the history would be lost. Is there some recommended way to do this?

We have a cvs2svn.py repository converter script. It works ok, but
may have some bugs, and doesn't yet convert cvs branches or tags.
Look in our source tree, in tools/cvs2svn/. We're still working on it.

> Also, other then the 'inconveniences' listed, are there any other
> glaring usability issues that would hamper subversion used in an actual
> corporate production environment?

Only that Subversion is still in Alpha. Many people are using it for
doing Real Work. Still, it might be unfair (at this moment) to
compare the nascent Subversion against the incredibly time-tested
CVS. :-)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Sep 10 04:55:15 2002