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

RE: Re: Communication of LOCKS and CHANGES

From: Bicking, David (HHoldings, IT) <David.Bicking_at_thehartford.com>
Date: 2007-11-26 17:54:49 CET


> -----Original Message-----
> From: Les Mikesell [mailto:lesmikesell@gmail.com]
> Sent: Wednesday, November 21, 2007 4:16 PM
> kmradke@rockwellcollins.com wrote:
> >
> > Providing "File is locked by someuser. Status was last checked on
> > 9:07am, Nov. 21, 2007 CST"
> > information without having to contact the server would be useful
> > information to my users and it explicitly informs them when the
> > information was last gathered.
> And the converse? If the lock didn't exist when that check
> was done but was subsequently created? Even if you check in
> real-time, unless you create your own lock you have no reason
> to believe that someone else won't lock before you start your changes.

Then, as I said multiple times before, you are no better or worse off than you are now, and a prerequisite of using Subversion is understanding the business model. When that happens, you have to do the merge and hope it isn't brutal. Life goes on.

On a side note, if it's been a while since your last update, you'd do well to update and see if the situation changed anyway. In this scenario, you'd have avoided the problem.

Let's just drop the fašade. You all are against doing this for philosophical or personal reasons, not because of any (voiced) technical concerns. I can live with that, it's your choice, and you're doing the work. I just don't like seeing all sorts of unsubstantiated assertions thrown around. In fact, it's the only reason I continue to follow-up.

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 Mon Nov 26 17:55:56 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.