Ben Collins-Sussman wrote:
>
>
>If locks were regular versioned properties, I guess I'd be annoyed at
>running 'svn up' and seeing millions of "_U" codes come down every
>day. It somehow violates my intuition about locks; I feel like locks
>should be a super-lightweight communications system, just an ephermal
>layer smoothly floating above the filesystem. They're not important
>enough to record and remember over time. Do I *really* care that on a
>certain date, certain people were communicating in a certain way? Not
>me, at least. Versioning the state of the communication system feels
>way too heavy and cumbersome to me.
>
>
Another problem is that in addition to locking excluding offline
operation (you cannot determine if a file is locked or attempt to gain a
lock if you cannot talk to the server), lockable files will be required
to always be up to date when editing. Since svn allows files to be at
different revisions in the working copy, this might not be that big of
an issue, but I thought I'd bring it up.
Adding the lockable propertly to a file also won't affect people until
they update to the latest revision.
-David Waite
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Aug 13 20:08:35 2002