RE: Communication of LOCKS and CHANGES

> -----Original Message-----
> From: Harvey, Edward [mailto:Edward.Harvey@patni.com]

> (Does anybody know why, recently my mail to this list has not
> been reaching the list?)

I think this is the second copy I saw.

>
> Many times before, people have had misconceptions about what
> a lock is, and how it should be handled. I'm not going to
> talk about what it is, because I'm assuming the interested
> people already know this. Instead I'm talking about what can
> be done to communicate this better, to the average unsuspecting user.
>
>
> #1
----snip----

I agree with these observations, and reiterate that it is very useful
for peers to see when files are locked, and by whom. I don't really
care how it is done. Since the feature is useful to all IDE plugins and
integrations, it makes sense to consolidate the logic in the core
system, rather than force all integration clients to implement their own
technique (in this case by a combination of "update" and "status -u" and
proprietary local cache files).

Personally, if I see a file I want is locked, the first thing I will do
is "update" and see if it is still locked. Then I can take action or
postpone my work. Right now, I don't see that it is locked until I try
to commit it or I _remember_ to explicitly check for locks.

--
David
*************************************************************************
This communication, including attachments, is
for the exclusive use of addressee and may contain proprietary,
confidential and/or privileged information.  If you are not the intended
recipient, any use, copying, disclosure, dissemination or distribution is
strictly prohibited.  If you are not the intended recipient, please notify
the sender immediately by return e-mail, delete this communication and
destroy all copies.
*************************************************************************
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org