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

Re: Lock Stealing Questions

From: Tim Hill <tim_at_realmsys.com>
Date: 2005-06-09 03:41:30 CEST

Well, I ran it again and this time I got what I expected -- the commit
*did* clear the lock and L1 showed a broken lock. So put this one down
to driver error :(

Sorry to waste your time.


Ben Collins-Sussman wrote:

> On Jun 8, 2005, at 5:09 PM, Tim Hill wrote:
>> 6. Check the status on both copies again. Oddly, it's unchanged: "K"
>> in L2 and "T" in L1. I did *not* expect this; I *thought* the commit
>> was supposed to remove the lock, but somehow the stolen status in L1
>> seems to have blocked this behavior. Is this by design?
> You lost me on step 6, I can't reproduce. For me, the commit *does*
> release the lock.
> I believe this is a bug specific to the ra_svn (svn://) module, and
> was already fixed. Are you sure that you're using a 1.2.0 client and
> server, and not some 1.2.0 release candidate?

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jun 9 03:43:37 2005

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.