[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Question re: svn "Needs-Lock"

From: Andy Levy <andy.levy_at_gmail.com>
Date: Mon, 22 Apr 2013 15:34:35 -0400

On Mon, Apr 22, 2013 at 3:30 PM, Ahmed, Omair (GE Oil & Gas) <
omair.ahmed_at_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

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.
Received on 2013-04-22 21:35:47 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.