Julien TOUCHE wrote:
> i want to change the way developpers has expanded the well-organized
> repository i have prepared for them. (like redbook)
> 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.?.?
> 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.
Unless the old history is of absolutely no value, the most logical path
would be to use a series of moves to achieve your desired tree layout.
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.)
Most of your developers will need to svn switch --relocate their working
copies to match the new layout. In some instances, clean checkouts might
> 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 ? :)
Interested in a hosted SVN repository? Email me, let's talk...
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Tue Apr 12 05:19:20 2005