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

Re: Issue 533 - locking

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2003-07-28 18:09:45 CEST

"D.J. Heap" <dj@shadyvale.net> writes:

> Here's a little patch to implement the core of kfogel's remarks in Issue
> 533 on locking. Basically it just stops the commit if a node has
> the svn:locked property set to a username other than the committer's.

As jerenkrantz already pointed out: last November, a great number of
svn developers met at ApacheCon and came up with a very complex,
post-1.0 locking system, documented in notes/.

Regarding this patch, I have one question: why can't this be done
with a pre-commit hook script? Your company can invent their own
property ("mycompany-lock:author"), attach it to files, and your
custom pre-commit hook can look for the property on changed-files in
the transaction. If present, disallow the commit.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jul 28 18:13:23 2003

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

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