[MERGE][#291046] Fix pushing an unstackable branch + stackable repo when there is a default stacking policy.

[Martin Albisetti]

On Tue, Dec 16, 2008 at 4:37 PM, John Arbash Meinel
<john at arbash-meinel.com> wrote:
> You can only get this if you already upgraded the repository to a
> stackable format. And I think it is just the fact that:

While we started moving to stacked branches in Launchpad, we stumbled
a dozen times into this same scenario. Upgraded repo, but not the
branches. Since we can't upgrade repo + branches easily with bzr (we
should!), it's very prone to be in a confusing situation with formats.
I think that upgrading for the user is reasonable, given we tell them
what we're doing and why (which I think this patch doesn't do).
Could we add a message telling the user we're upgrading for them
because they're trying to use stacking with an unsupported format?



-- 
Martin