[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: Nicolás Lichtmaier <nick_at_panoptico.reloco.com.ar>
Date: 2005-02-03 04:37:00 CET

>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.

Sorry to disturb, but... shouldn't the read-only status of the file tied
to the property state *on the repository*? So, a propset adding the
property wouldn't do anything, the commit would make the file read-only
instead. What's the point of having an uncommited "svn:needs-lock"
forcing a local read-only file when everybody else can still freely
commit it?

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Feb 3 04:38:46 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.