Stacking policy

Robert Collins robertc at
Thu Apr 10 04:58:48 BST 2008

On Tue, 2008-04-01 at 11:48 -0400, Aaron Bentley wrote:
> 0. If the user specifies a stacking policy, select that policy.
> 1. Open containing folders looking for a shared repository or stacking
>    configuration.  If a shared repository is found, select that shared
>    repository.  If a stacking configuration is found, select that
>    policy.
> 2. If no policy has been selected, and the branch is being created
> from
>    another branch (i.e. bzr branch), and the other branch has the same
>    URL prefix (including hostname, if applicable), select the other
>    branch as the stack-on branch.
> The justification is:
> 0. The user should always be in control
> 1. Remote sites should be able to enable revision sharing either using
>    shared repositories or stacking.
> 2. Branches on the same machine are usually equally visible, so access
>    to one implies access to the other.

I like all but 2. My only concern is that this will change the behaviour

bzr branch lp:foo foo
bzr branch foo bar
rm -rf foo

I think we may cause the same kind of 'history lost' situation arch had
with 2 as it stands.

GPG key available at: <>.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : 

More information about the bazaar mailing list