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

Re: Moving files from one repository to another

From: Ryan Schmidt <subversion-2008c_at_ryandesign.com>
Date: Wed, 1 Oct 2008 14:49:36 -0500

On Oct 1, 2008, at 3:33 AM, Miah, W (Wadud) wrote:

> I have two Subversion repositories and would like to retire one, only
> after I've moved over the files with the entire revision history to
> the
> new one. What process needs to be followed to achieve this?

There are two ways.

1. "svnadmin dump" the old repository and "svnadmin load" it into the
new repository. Disadvantages: revisions of the old repository will
be renumbered to fit into the new repository, so any references to
revision numbers in the old repository's log messages will be
inaccurate. You will have to throw away any working copies of the old
repository and check those paths out anew from the new repository
instead. Finally, the newly added revisions will probably cause the
new repository's revisions to not all be in chronological order,
which means you can't use the "-r{date}" revision syntax. If you care
about the date revision syntax, try method 2:

2. "svnadmin dump" both existing repositories. Use "svndumptool.py
merge" [1] to combine the two dumpfiles in chronological order.
"svnadmin create" a new repository and "svnadmin load" the merged
dumpfile into it. Disadvantages: pretty much all revisions will be
renumbered, so any references to revision numbers in your log
messages from either existing repository will be inaccurate. And you
will need to throw away working copies of either repository and check
out new ones.

[1] http://svn.borg.ch/svndumptool/

To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-10-01 21:50:13 CEST

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.