You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by "Ahmed, Omair (GE Oil & Gas)" <om...@ge.com> on 2013/04/22 21:30:21 UTC
Question re: svn "Needs-Lock"
Hello,
Is "Needs-Lock" the correct (or expected) mechanism by which to make a release tag immutable? Basically, I am looking for a way to "lock" a tag to prevent accidental updates.
Thanks.
Omair
Re: Question re: svn "Needs-Lock"
Posted by Andy Levy <an...@gmail.com>.
On Mon, Apr 22, 2013 at 3:30 PM, Ahmed, Omair (GE Oil & Gas) <
omair.ahmed@ge.com> wrote:
> Hello,
>
> Is "Needs-Lock" the correct (or expected) mechanism by which to make a
> release tag immutable? Basically, I am looking for a way to "lock" a tag to
> prevent accidental updates.
>
> No. svn:needs-lock is an indicator for the SVN client that a file should
be marked as read-only until the user creates a lock in the repository. See
http://svnbook.red-bean.com/en/1.7/svn.advanced.locking.html
To make a tag immutable, you need to restrict access in the repository
itself. This is typically done via path-based authorization (deny write
access to the tag's path), or a pre-commit hook script (such as
svnperms.py) which rejects a commit which writes to that path.