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

Re: Locking functional spec: read-only WC

From: Garrett Rooney <rooneg_at_electricjellyfish.net>
Date: 2004-10-14 02:57:56 CEST

Jack Repenning wrote:

> I'm not sure about one thing, though: if there's no property, and if yet
> there's a lock, then does checkout/update (by someone not the locker)
> read-only-ate the file, as is done when the property is set? As nearly
> as I can see, locking-ui.txt does not say so (I would assume, then, the
> answer to be "no"). But it seems to me that the presence of an actual
> lock, regardless of the "svn:must-lock" property, should force some
> additional discipline about the file.
> In other contexts, we sometimes talk about "advisory" vs. "compulsory"
> locks, where "advisory" locks only get in the way of people nice enough
> to check for them. Without the enforcement mentioned immediately above,
> these seem to be purely advisory locks (for files without the property,
> anyway)?

I don't like the idea of turning files read only like that. It seems
like we should either force the file to be read-only whenever you don't
have the lock, which the svn:must-lock property will provide, or not do
it at all. I don't like the inconsistency presented by having things
magically becoming read-only based on whether I've run 'svn update'. It
just feels wrong. I'd prefer to go either all one way or all the other,
on a per-file basis, controlled by the property.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Oct 14 02:58:06 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.