bzr upgrade and shared repos

[Viktor Nagy]

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


2009/2/18 John Arbash Meinel <john at arbash-meinel.com>

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> 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
>
> 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 - http://enigmail.mozdev.org
>
> iEYEARECAAYFAkmcQXoACgkQJdeBCYSNAAM3VQCfS3HbMmJMKLD/spdlHuVOJy69
> ZxQAoNDhvxe8vRAlsCwjX6mT9oD3YBe/
> =LapN
> -----END PGP SIGNATURE-----
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ubuntu.com/archives/bazaar/attachments/20090218/f7c56d2c/attachment.htm