Ben Collins-Sussman wrote:
>
> On Nov 17, 2004, at 12:10 AM, Robert Hunter wrote:
>
>>
>> Alice checks out revision 10.
>> Bob checks out revision 10.
>> Alice accepts a task that requires modifying a file,
>> "non-versionable.png".
>> Alice runs an update, but her working copy is already up to date.
>> Alice sets an attribute "read-only", perhaps with her username as a
>> value.
>> Alice commits revision 11.
>> Alice begins working on the file.
>> Bob accepts a task that requires modifying the same file.
>> Bob runs an update, and receives the new "read-only" attribute.
>> Bob's client sets local filesystem permissions on the file to read only.
>> Bob begins work on the file, but his editor informs him the file is
>> read-only.
>> Alice finishes work on the file.
>> Alice removes the "read-only" attribute.
>> Alice issues commits revision 12.
>> Bob updates to revision 12.
>> Bob's client sets the local filesystem permissions on the file to
>> read/write.
>>
>
> You've effectively just described how our upcoming 1.2 'locking'
> feature is going to work, the thing I've been working on for the last
> month or so.
Not quite. :-) He described how shared locks could concievably work, but
we punted on shared locks ages ago and decided to only implement
exclusive locks.
-- Brane
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Nov 18 13:15:40 2004