actually, first I would have expected that upgrading the repo will upgrade all its branches as well. Even though I have some ideas why this is not the best thing to have, it might be good to have it implemented with a flag for example. It would make it much easier to upgrade many branches in a repo. V <div class="gmail_quote">2009/2/18 John Arbash Meinel <<a href="mailto:john@arbash-meinel.com">john@arbash-meinel.com</a>> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 <div><div></div><div class="Wj3C7c"> Viktor Nagy wrote: > I was playing around with upgrade to understand how it works exactly, > and it was strange to me. So others might find this info useful as well. > > The main conclusions are > * ``bzr upgrade . --1.9`` on a shared repo won't upgrade your branches > below the repo. > * after ``bzr upgrade . --1.9`` creating a new branch shows > format:unknown for ``bzr info``, but > * ``bzr upgrade . --1.6`` in the new shared repo actually upgrades to > 1.9, WITHOUT ANY NOTICE! > > Upgrading a branch without its repo does not affect the repo in any ways. > > V </div></div>The branch format 1.6 is identical to the *branch* format 1.9. The problem is that "bzr info" is giving you the summary of all formats (repo + branch), which can combine in various ways. The reason we give "unknown" is because a pack-0.92 branch format with a 1.9 format repository doesn't have a simple combined format name. John =:-> -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Cygwin) Comment: Using GnuPG with Mozilla - <a href="http://enigmail.mozdev.org" target="_blank">http://enigmail.mozdev.org</a> iEYEARECAAYFAkmcQXoACgkQJdeBCYSNAAM3VQCfS3HbMmJMKLD/spdlHuVOJy69 ZxQAoNDhvxe8vRAlsCwjX6mT9oD3YBe/ =LapN -----END PGP SIGNATURE----- </blockquote></div>