Bazaar Mercurial Plugin to access BitBucket

[Stephen J. Turnbull]

Eli Zaretskii writes:
 > > From: "Stephen J. Turnbull" <stephen at xemacs.org>

 > > In the bound branch, the developer is stuck with the choice of
 > > saving up her changes [...] or interleaving her commits [...]. 

 > You can use "bzr ci --local" to avoid the above disadvantages.

True.

 > Although, if you feel compelled to do that for the above reasons, you
 > should really make a local branch ;-)

That's not clear to me.  If used occasionally and it works for the
developer, it seems to combine the best of both worlds: your --local
commits are recorded in their development context, and when you do a
regular commit they're serialized appropriately in the remote repo.

The defect I see in this workflow is that the user ends up making a
lot of decisions: when to use --local vs. not, and when to do the
merge from the remote to allow a commit to work, at least.  In other
words, instead of letting Bazaar manage your workflow, you do it
yourself.  This dilutes the "many workflows" advantage of Bazaar
substantially.

It might be a useful "escape" workflow in a workplace where you have a
Bazaar expert on call to handle those decisions on the (rare)
occasions they seem called for.