Chris Jensen wrote:
>>> Could you clarify? I'm not sure exactly what you are asking.
>>
>>
>> Suppose I have a repositoy on a mounted drive with autoversion
>> enabled. I could also checkout a separate working copy and make
>> changes/commit files manually -- for example, making a change to
>> foo.doc. Then, if someone edits foo.doc on the network drive, the
>> autocommit *could* fail because the revision is not up to date.
>>
>> I guess I should check this by myself, anyway :)
>
> Isn't this what locking in 1.2 is supposed to solve?
> If the webdav client is well behaved then it should get a lock on
> foo.doc when it's opened for editing, and then the user trying to commit
> from the working copy should be prevented because they don't have a lock?
> Isn't that how it works?
But, if you consider the case of a general text editor, and a webdav mount,
the webdav components are unaware of the editing session, so locking cannot
occur.
Max.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Jun 12 12:15:24 2005