[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: Greg Hudson <ghudson_at_MIT.EDU>
Date: 2005-02-02 23:46:32 CET

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.

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

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.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Feb 2 23:47:44 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.