Re: Locks on the Bzr repository

[Andreas Schwab]

Eli Zaretskii <address@hidden> writes:

>> From: Andreas Schwab <address@hidden>
>> Date: Thu, 19 Aug 2010 17:52:53 +0200
>> Cc: address@hidden
>> 
>> Stefan Monnier <address@hidden> writes:
>> 
>> > If that's indeed the culprit, I think it's a misfeature of Bzr, but at
>> > least we can workaround it by using "bzr commit -m <...>", which I would
>> > then *strongly* recommend.
>> 
>> Even better: use an unbound branch.
>
> How would this help?  No matter what you do in an unbound branch, you
> eventually need to push or merge, at which time you will have the same
> problem.  What am I missing?

It won't improve the actual transfer of the commits, but it lets you
review before you push.

Andreas.

-- 
Andreas Schwab, address@hidden
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."