And once you have this new repository, you will need to throw away
your old working copies from the old repository, and check out new
working copies from the new repository. There's no way to reassociate
the old working copy with the new repository, since the new
repository's internal ID is different from the old repository, and to
the client, the new repository is not similar to the old one.
On Oct 21, 2007, at 08:48, Rob van Oostrum wrote:
> You need to 'svnadmin dump' your repository and pipe it through
> svndumpfilter to only include the tree you want. If you run into
> entanglements where files inside your project were copied/moved from
> somewhere else in your repository, you may want to look at
> svndumpfilter3.
>
> http://svnbook.red-bean.com/en/1.4/svn-
> book.html#svn.ref.svnadmin.c.dump
> http://svnbook.red-bean.com/en/1.4/svn-
> book.html#svn.reposadmin.maint.tk.svndumpfilter
> http://furius.ca/pubcode/pub/conf/common/bin/svndumpfilter3.html
>
> On 10/21/07, Sander Marechal wrote:
>
>> What is the best way to relocate a project in subversion across
>> servers
>> *and* repository path at the same time?
>>
>> Currently I have multiple projects inside a single repository on
>> server1. I would like to spin-off one of these projects into a
>> repository of it's own on server2. E.g, from:
>>
>> https://server1.example.com/my-repository/my-project/(branches|
>> tags|trunk)
>>
>> to:
>>
>> https://server2.example.com/my-new-project-repository/(branches|
>> tags|trunk)
>>
>> What's the best way to do this?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Oct 21 23:19:10 2007