[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Module Migration

From: Garrett Rooney <rooneg_at_electricjellyfish.net>
Date: 2006-01-19 21:53:39 CET

On 1/18/06, Ryan Schmidt <subversion-2006Q1@ryandesign.com> wrote:
> 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.

That will still break date-based revision specifications, there is
currently no way to incrementally migrate cvs projects into a
subversion repository without breaking date-based revision


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jan 20 01:14:14 2006

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.