On Jan 18, 2006, at 18:49, Dan Bush wrote:
> I want to migrate CVS modules into SVN on a project by project basis.
> I was going to use cvs2svn and the "One project at a time" methodology
> (http://cvs2svn.tigris.org/cvs2svn.html#convert) but, the possibility
> of breaking the date-based range commands is unacceptable. I would
> like to bring up a secondary SVN repo, use cvs2svn to migrate a CVS
> module to it, ensure nothing is broken; then extract it (with history)
> and import it into the actual SVN repo. Bringing up a secondary SVN
> instance as a migration staging point is trivial but, is there a way
> to migrate an individual module from one SVN repo to another.
> Import/export is great but does not include history.
svnadmin dump from the secondary repository, svnadmin load into the
primary repository, possibly specifying the path where it should go
with --parent-dir.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jan 19 03:30:36 2006