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

Re: Best Practices question

From: Vladimir Prus <ghost_at_cs.msu.su>
Date: 2002-10-09 18:01:37 CEST

Rafael Garcia-Suarez wrote:
> Jeff Stuart <furball@weboverdrive.com> wrote:
>
>>Easy. :) Import one repository into the other.
>
>
> This way you'll lost the history of the imported project.
>
> It should be possible to produce a list of patches (by
> svn diff -rN:N+1) for the old repository, and commit them
> to the 2nd repository.
>
> Caveats : metadata, copies, renames -- I don't know how
> svn will handle this. Apparently svn diff doesn't give
> any hints about copies or renames.
>
> Another possibility : hack the output of svn dump. But
> perhaps that's total nonsense.

I don't think it's nonsense. You can 'svnadmin dump' one repository and
then 'svnadmin load' the data into another repo. Revision number will be
different but the history will be preserved. I've tried that with
repositiory produced by cvs2svn.py and it worked fine.

- Volodya

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Oct 9 18:03:18 2002

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

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