Re: bzr repository ready?

[Stephen J. Turnbull]

Eli Zaretskii writes:

 > Thanks for the explanations.  So what would be the workflow of an
 > Emacs hacker who also has write access to the master repository, with
 > stacked branches?

There is no such workflow.  For developers, stacked branches are a
space optimization at the expense of great inconvenience in all
accesses to history, including bzr log and bzr diff.  When using one
of the more specialized workflows that Óscar and Jason have described,
you'd use checkouts or bound branches, not stacked branches.

Stacked branches were recommended for *beta testers* because it makes
the transition from tester to occasional hacker much easier than with
a checkout, but they have much less immediate need for convenient
access to history than the kind of hacker who becomes a committer.