You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by "O'Hearn, Mike" <Mi...@jenzabar.net> on 2005/06/22 20:19:15 UTC
Locking to prevent changes to a branch?
I want to prevent from accidental changes to an old branch. We are new to
subversion and I find that a lot of people accidentally work in the wrong
working copy.
Is locking the entire branch a good solution? Any downsides to this? Any
other suggestions?
Re: Locking to prevent changes to a branch?
Posted by kf...@collab.net.
"O'Hearn, Mike" <Mi...@jenzabar.net> writes:
> I want to prevent from accidental changes to an old branch. We are new to
> subversion and I find that a lot of people accidentally work in the wrong
> working copy.
>
> Is locking the entire branch a good solution? Any downsides to this? Any
> other suggestions?
It's a good solution, but consider moving that branch to the 'tags/'
directory and locking it down there. I believe svnbook.red-bean.com
goes into detail on this.
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Locking to prevent changes to a branch?
Posted by David Weintraub <qa...@gmail.com>.
There is a script that comes with the Subversion source called
commit-access-control.pl that will do exacly what you want. Simply
setup your pre-commit hook to run this script, and setup a control
file that will prevent people from committing changes in that
directory.
It's fairly easy to setup and use.
--
David Weintraub
qazwart@gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org