[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Communication of LOCKS and CHANGES

From: Reedick, Andrew <jr9445_at_ATT.COM>
Date: 2007-11-29 17:05:27 CET


> -----Original Message-----
> From: kmradke@rockwellcollins.com
> [mailto:kmradke@rockwellcollins.com]
> Sent: Tuesday, November 27, 2007 11:54 AM
> To: Reedick, Andrew
> Cc: users@subversion.tigris.org
> Subject: Re: Communication of LOCKS and CHANGES
> You are assuming I want to know what files are safe to work
> on. I want to know what files are POTENTIALLY unsafe to work
> on. I will check the repo if I want the true status. People
> work in different ways.

> You said the information "is useless", but then gave an
> example where it was useful...

Relying on cached lock information implies that you do not care about
locks in the first place.

I) If I run status/update 5 minutes after someone placed a lock, then
the Locker and I win.

II) If I run status/update 5 minutes _before_ someone places the lock,
        a) an (exciting?) merge will need to be performed and either

                b1) the Locker gets chastised for not notifying people
(via email) that a major change was being done and that anyone else
already working on the file needed to coordinate with the Locker.
(Locked for a reason.)

                b2) or, if there is no need to chastise the Locker then
everyone is following or accepts SVN's standard copy-modify-merge
paradigm, in which case, there was no need to lock the file in the first
place. (Locked for no reason.)

In short, relying on cached lock information implies that you do not
care about locks in the first place.

This problem also applies to 'svn lock'. So the only "rational" way to
use locking in SVN is to a) communicate locks outside of SVN (email,
etc.,) or b) use 'needs-lock'.

To go back to Mr. Bicking's roof analogy. People aren't saying that a
meteor-proof roof is the only viable solution worth pursuing (perfect
roof or nothing.) Instead, we're trying to say that cached lock info is
similar to building a small section of roof on rails, and then sliding
that section of roof over you as you move from room to room. Your head
may stay dry, but you will still end up sitting on wet furniture.
Sliding roofs (and cached lock info and 'svn lock') do not solve the
problem of why you need a roof in the first place.


The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential, proprietary, and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from all computers. GA623

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Nov 29 17:06:33 2007

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.