Re: The "svn:needs-lock" property

Ben Collins-Sussman wrote:

>> I think we should _not_ require a lock in order to commit, either
>> from WC or server side.
>
> Agreed. But in the case of WC, the only way the file can change from
> read-only to read-write by locking it first, so files that have this
> property generally *will* be locked already when committed.

So anyone can circimvent this by simply chmod'ing the file?

> I think this whole section needs to be changed; as I said, I think
> I'm with you. The presence of the property shouldn't *require* a lock
> to make changes. The property should just affect working copy
> permissions, that's it.

I'd just like to point out that, given the way Subversion identifies
files, if locking affected the ability to delete a file, it would be a
lock on the parent directory, not the file itself. Just like you can
delete a non-writable file on Unix as long as its parent is writable.

-- Brane

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Dec 15 12:18:29 2004