On May 31, 2005, at 11:27 AM, Ben Collins-Sussman wrote:
>
> On May 31, 2005, at 10:07 AM, Markus Dehmann wrote:
>
>
>> We want to change the layout of our project and make it as
>> painless as
>> possible for the people working on it.
>>
>> Here is the change we want to make:
>> /repos/module1
>> /repos/module2
>> will become
>> /repos/project/trunk/module1
>> /repos/project/trunk/module2
>>
>> As it stands now, people have checked out module1 and module2 with
>> two
>> 'svn co' commands.
>>
>> What's the best way to make the change?
>>
>
> Don't mess with working copies at all; just issue a series of
> server-side commands:
>
> svn mkdir URL-to-/repos/project
> svn mkdir URL-to-/repos/project/trunk
> svn mv URL-to-/repos/module1 URL-to-/repos/project/trunk/
> svn mv URL-to-/repos/module2 URL-to-/repos/project/trunk/
>
>
>
>> Afterwards, everyone has to checkout a new copy:
>> svn co file:///repos/project/trunk/ project
>>
>> Is that right?
>>
>
>
> Users can either checkout fresh working copies, or they can 'svn
> switch' to the new location:
>
> svn switch URL-to-/repos/project/trunk/module1
But how can they get the parent folder of their module1 and module2
working copies to become a versioned folder representing 'project/
trunk' without needing to check in their changes?
E.g.
> ls
module1 module2
[where '.' is not a working copy, but module1 and module2 are.]
Would this do it?
> svn co -N URL-to-repos/project/trunk .
Scott
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue May 31 17:47:05 2005