Pulling multiple branches in the same repository

[Martin Pool]

On  8 May 2006, Aaron Bentley <aaron.bentley at utoronto.ca> wrote:
> Martin Pool wrote:
> 
> >We do wait for some time for the lock; we just don't communicate it  
> >very well.  What I mean is
> >
> >  "waiting 30s for lock held by foo at host...."
> >
> >and then C-c should interrupt it properly.
> 
> I get the distinct impression that we don't wait on pull.  Instead, it 
> seems as though we lock the branch, try and fail to lock the repository, 
> and throw, leaving the branch locked.

I think the lock on the destination branch is taken by the
needs_write_lock decorator on BzrBranch.update_revisions, and that
should work properly.  But it is strange that we would get this message.
Perhaps the lock can remember the frame where it was acquired.

-- 
Martin