>>
>> i want to change the way developpers has expanded the well-organized
>> repository i have prepared for them. (like redbook)
>>
>> ===
>> proj1
>> tags
>> branch
>> trunk
>> proj2
>> tags
>> branch
>> trunk
>> ===
>>
>> in
>>
>> ===
>> proj1
>> tags
>> branch
>> trunk
>> trunk2
>> data1a
>> data2b
>> data1
>> data2
>> proj2
>> tags
>> branch
>> trunk
>> proj3
>> folder1
>> folder2
>> ...
>> proj4
>> tags
>> branch
>> trunk3
>> data1c
>> data2c
>> ===
>>
>> so i have a lot of move to do, but my main problem is something which
>> for me is one project with 2 branchs and is there, 2 projects
>> (proj1/trunk, proj4/trunk3) and a tree in a tree (trunk2 in trunk)
>
>
> I wasn't able to determine if the second tree diagram was the existing
> or the to-be-achieved layout.?.?
no. this is the current status made by developpers
new one would be
===
proj1
tags
branch
branch-trunk2
branch-trunk3
trunk
data1
data2
proj2
tags
branch
trunk
proj3
tags
branch
trunk
===
> I suggest you hotcopy/backup the repository and work out the migration
> path in a private environment before you spring it on the developers. If
> after testing, you feel it can all be done in a short period of time,
> send everyone to lunch at once and spend the hour tweaking the
> repository. (Checking in all updates might not be a bad idea.)
why not, after testing, load a dump of the test/new tree in main svn
server ?
thanks
Regards
Julien
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Apr 12 06:15:51 2005