On Apr 4, 2007, at 18:46, Dave Cardwell wrote:
> Yuji Shinozaki wrote:
>
>> On Apr 4, 2007, at 11:19 AM, Dave Cardwell wrote:
>>
>>> I have a repository with the following structure:
>>>
>>> /foo
>>> /foo/branches
>>> /foo/tags
>>> /foo/trunk
>>> /bar/
>>> /bar/branches
>>> ...
>>>
>>>
>>> I'm attempting to migrate these individual sub-folders (foo,
>>> bar, ...) to their own Google Code project hosting repository,
>>> while maintaining their revision history.
>>>
>>> I've attempted to use svnsync as per http://code.google.com/
>>> support/bin/answer.py?answer=56673&topic=10386 but evidently
>>> svnsync can only work with entire repositories as it refuses to
>>> sync the individual folders.
>>>
>>> What's the best way of going about this?
>>
>> You could do a svn mv in the existing repo to put the directories
>> into the structure you want, and then do the svnsync...?
>
> The problem is that I only want one directory in the repository at
> a given time. Perhaps I could do delete others, move, sync, revert,
> repeat for each sub-folder, but I was hoping there was a more
> elegant solution.
Subversion provides the svndumpfilter program to help you... You can
"svnadmin dump" your entire local repository. Then "svndumpfilter" to
filter out specific parts of the repository that you want to keep.
You can "svnadmin create" local repositories for each part that you
want to eventually move to Google Code. "svnadmin load" the filtered
dumpfiles for each part into the local repository. Finally, sync each
local repository with Google Code. Then presumably you can remove the
temporary local repositories you created.
--
To reply to the mailing list, please use your mailer's Reply To All
function
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Apr 5 07:26:59 2007