Stacking policy

[James Westby]

On Wed, 2008-04-02 at 12:22 -0400, Stefan Monnier wrote:
> When working across hosts, it might make sense to use stacking by
> default (although you'd first want to make sure that Bzr can use the
> branch even when the remote host is unavailable).

Stacked branches can't do this, that's lazy or shallow branches.
Stacked branches prepare a lot of the ground for them to exist,
but they are not the same.

> 
> Whichever default is chosen, it might be a good idea to provide
> a half-way solution in the form of a --lazy flag: it would create
> a stacked branch, and then just before returning, it would fork a `bzr
> reconfigure' to make the branch non-stacked.
> 

I don't understand how this is different to a normal "bzr branch", you
just end up with a normal branch either way.

Thanks,

James