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

Re: problem splitting a repository

From: Ryan Schmidt <subversion-2006Q1_at_ryandesign.com>
Date: 2006-02-03 20:26:02 CET

On Feb 3, 2006, at 20:07, Jim Alateras wrote:

>> U=url://to/repository
>> svn mkdir $U/project1 -m "Making empty project1 directory"
>> svn mkdir $U/project2 -m "Making empty project2 directory"
>> svn mkdir $U/project3 -m "Making empty project3 directory"
>> svn mv $U/trunk/project1 $U/project1/trunk -m "Moving project1 trunk"
>> svn mv $U/trunk/project2 $U/project2/trunk -m "Moving project2 trunk"
>> svn mv $U/trunk/project3 $U/project3/trunk -m "Moving project3 trunk"
>> svn mv $U/branches/project1 $U/project1/branches -m "Moving
>> project1 branches"
>> svn mv $U/branches/project2 $U/project2/branches -m "Moving
>> project2 branches"
>> svn mv $U/branches/project3 $U/project3/branches -m "Moving
>> project3 branches"
>> svn mv $U/tags/project1 $U/project1/tags -m "Moving project1 tags"
>> svn mv $U/tags/project2 $U/project2/tags -m "Moving project2 tags"
>> svn mv $U/tags/project3 $U/project3/tags -m "Moving project3 tags"
> Ryan, will this approach also give me all the history.

Absolutely, the history is retained. Subversion is designed to always
preserve history—to make it largely impossible to lose anything. I
don't think there's any svn command that can lose history (other than
setting revision properties, but that feature has to be explicitly
enabled on the server side if it's desired). svnadmin commands, on
the other hand, can lose history (like dumping and then reloading a
subset), which is why they must be performed by an admin with local
access to the server's filesystem.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Feb 3 20:34:50 2006

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