[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-30 20:32:18 CET

> -----Original Message-----
> From: Les Mikesell [mailto:lesmikesell@gmail.com]
> Bicking, David (HHoldings, IT) wrote:
> >
> > As stated much earlier
> >
> (http://subversion.tigris.org/servlets/ReadMsg?listName=users&msgNo=72
> > 19 4), I'm not talking about unmergeable files. Stop acting as if I
> > want unserialized access to files that require serialization.
> You've lost me completely then. If concurrent work can still
> proceed usefully, exactly what is it that you expect an
> observer of a temporary lock to do?

Sure, review this message again:

Specifically, review this part:

===== begin block quote ====
Add to that the user id, and you know both who is radically altering the
file, and why. Given this information, if you've not yet started work
on that class, you might decide to:

1) postpone your change until the file is unlocked (talk to the lock
2) point out to the lock holder that you have a deadline, and negotiate,
possibly bringing in management.
3) send a patch to the lock holder, requesting she merge it in before
things get too hairy.
4) talk to your manager and ask why you weren't told about this work
before you started your task.
===== end block quote ====

And now I add

5) continue as normal and not worry about merging

Regardless of the choice I make, I have to wait for the lock release
before I can commit. Knowing the file is locked should clue me in to
the probability that major merge is in my future. Maybe I want to
mitigate that.

I'm sure there are other options.

> --
> Les Mikesell
> lesmikesell@gmail.com

David Bicking
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 Fri Nov 30 20:33:02 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.