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

Re: RFC: locking-design.txt, On non-locking policies

From: Greg Hudson <ghudson_at_MIT.EDU>
Date: 2004-08-28 02:55:28 CEST

On Fri, 2004-08-27 at 19:40, Alex Holst wrote:
> Someone on IRC, don't recall whom, recently asked me to voice this
> request on dev, and I thought this addition to locking-design.txt
> describe my wishes best.

Unfortunately, you copied text by brane which didn't really make sense.
Nobody's done anything about it because it's never clear how to respond
to brane's weird "comments inside design documents" habit.

  * "Liveprop" is a DAV-specific term, as best I understand it, and
doesn't belong in the locking design.

  * The idea that the unmergeability of a file is "a repository policy,
not a user decision" is bizarre. All file properties are "repository
policies," but the repository belongs to a set of users (some perhaps
more privileged than others).

What you really want is a way to prevent people from locking
files--ideally specific files, but perhaps a blanket protection on the
whole repository might be enough--and you don't care how it's
implemented. I assume we'll have at least the blanket protection
ability in the initial locking implementation.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Aug 28 02:55:40 2004

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.