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

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Martin Albisetti wrote:
> 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?
> 
> 
> 

If you do "bzr branch --stacked" or "bzr push --stacked-on" it already
informs the user if it is upgrading the branch format.

This patch doesn't add it, because we already did it.

John
=:->

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAklH97cACgkQJdeBCYSNAAP17QCffF1xlNf4EI6V/OTJE63qjjcF
R5cAoICaPZfZnBcPaca69XinU1ZjE7eF
=daRS
-----END PGP SIGNATURE-----