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

Re: Locking: RFC: svn:needs-lock behaviors

From: Brian W. Fitzpatrick <fitz_at_collab.net>
Date: 2005-02-03 00:25:44 CET

On Feb 2, 2005, at 4:46 PM, Greg Hudson wrote:

> On Wed, 2005-02-02 at 16:53, Brian W. Fitzpatrick wrote:
>> Propset:
>> - Setting the svn:needs-lock property sets the file to read-only
>> (It also canonicalizes the value to '*')
> Only if the file is unlocked.

Ah yes. Right.

> Where did you get the canonical value '*' from?

I modeled it after svn:executable.

> Setting svn:needs-lock on an unlocked modified file, or unlocking an
> svn:needs-lock file which has been modified, both seem like error
> conditions to me. The user should not be able to, without manually
> breaking the read-only flag, get the working copy into a state where
> there is an svn:needs-lock file which is locally modified and unlocked.

OK. That seems to be the consensus (from Mark, Peter, yourself, and
Philip), so I'll tweak the mini-doc with everyone's suggestions and


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Feb 3 00:27:59 2005

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.