[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: Bicking, David (HHoldings, IT) <David.Bicking_at_thehartford.com>
Date: 2007-11-20 18:52:11 CET

> -----Original Message-----
> From: Les Mikesell [mailto:lesmikesell@gmail.com]
> Bicking, David (HHoldings, IT) wrote:
> > Given the above it makes sense that:
> > ====================================
> > 1. A developer who wants to make a change to a file might
> have to do
> > extra work if he makes those changes, attempts to commit, and finds
> > the file is locked. Why? If the locked file is later
> committed and
> > completely altered from his base copy, the merge effort is
> especially
> > painful.
> > 2. Said developer has no reason to specifically look for
> locks, since
> > the normal modus operandi is to edit, merge, and commit.
> I'm missing something here. If you are working with content
> that can't be merged, why is it normal operating procedure to
> do the work without obtaining a lock? Or in the problem
> case, why do only some people know to obtain the lock even
> though other people are working on the same file? Note that
> if it really is standard procedure not to lock, there won't
> be any locks for you to see anyway...

Yes, you are missing something here. Refer to #2 that you quoted, and
also to item #3, which for some reason you apparently didn't get to
before replying:

3. A lock is dynamically added to a file presumably due to unusal

It is possible to choose to lock a perfectly normal file, and there ARE
valid reasons to do so. To see an example, please go back and read the
paragraph following that list of points you quoted. When a person does
this, nobody else knows UNLESS that person decides to send a
distribution email to tell them, OR the team leader tells the other
committers in some fashion.

At no point - ever - did I imply that these files were "unmergable" or
had a "requires lock" property. If the file already has a property
attached that says "you must lock this to edit it", that information is
CURRENTLY visible in Ankh and Tortoise (immagine that!). Therefore, I
have no complaints about that particular feature.

presented to the developers in an easier to use format that requires
less work to attain. Why is that such a terrible thing? I am becoming
quite frustrated. Can someone at least acknowledge the points I'm
making, rather than set up a straw man and set fire to it?

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
Received on Tue Nov 20 19:14:40 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.