lock oddity

[Wichmann, Mats D]

bazaar-bounces at lists.canonical.com wrote:
> Jeff Licquia wrote:
>> Wichmann, Mats D wrote:
>>> for the purposes of fiddling around with this, how
>>> would one create a valid lock without having to try
>>> to kill a process in progress?
>> 
>> It might be easier to just query the lock status.  I found this in
>> the implementation of "bzr info":
>> 
>>     if (repository.get_physical_lock_status() or
>>         (branch and branch.get_physical_lock_status()) or
>>         (working and working.get_physical_lock_status())):
>> 
>> Since we don't care about the details of the lock, we should
>> be able to
>> streamline that a bit.
> 
> 
> hmmm, I tried his technique and bzr info doesn't show me the tree as
> locked 
> 
> it's locked, though....

Of course that was sent as if it were a private message, but
no need - I didn't see anything about locks in info while I
had the branch locked.