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

Re: I deserve flames, but need help regardless...

From: John Peacock <john.peacock_at_havurah-software.org>
Date: Wed, 11 Jun 2008 19:01:19 -0400

Joe Korzeniewski wrote:
> My question is: how do I move the file structure at the root into a new root
> trunk folder, yet maintain revision history.

It kind of depends on how large the repository is and how many working copies
there are. If the project is still in its infancy, and especially if you are
the only person who is using it, you could do a dump and reload into the
preferred layout:

        $ svnadmin create /path/to/newrepo
        $ svn co file:///path/to/newrepo/ wc
        $ cd wc
        $ mkdir trunk branches tags
        $ svn add trunk branches tags
        $ svn ci -m 'Create the structure'
        $ cd .. && rm -rf wc
        $ svnadmin dump /path/to/oldrepo > repo.dump
        $ svnadmin load --parent-dir trunk /path/to/newrepo < repo.dump

The reason why this might be the better solution is that your history will be
cleaner (there won't be any messy renames), so it is easier to look at the full
history of the repo.

This method will require you to throw away any existing working copies; this
repository will have a different UUID from the original, so there is no way to
convert the working copies to the new repo. Additionally, your revision numbers
will all be one higher, so if you have a habit of referring to the revision
number in log messages, this will mess you up.



To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-06-12 01:00:05 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.