Hi
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'm not sure, if it is better to
- create a new project, import from cleaned files and lost revisions/logs
- create a new project, move all stuff needed in trunk, create branchs,
merge other stuff in these branches and next delete old stuff
- try to make some miracles moves to reorganize correctly all this.
the second seems to be good but take time (even the first one, a lot
more for the third)
On a second point and to avoid this, i want to make more restrictive
permissions, so devs can't create stuff in root or first root folder.
i was thinking to remove classical unix perm from devs/apache group on
root or maybe use acl to have better granularity.
any advices to avoid developpers to make some mess in svn ? :)
thanks
Regards
Julien
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Apr 11 21:45:43 2005