Branch fails from 'pack-0.92' repo to 'rich-root-pack' repo

[Aaron Bentley]

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

Ben Finney wrote:
> Aaron Bentley <aaron at aaronbentley.com> writes:
>> The converter does not handle these rare halfway-rich branches
>> correctly yet. I hope to work on that this week. No released version
>> of Bazaar ever created such branches.
> 
> Okay. I look forward to a bugs-everywhere repository that I can work
> with.

I hope to work on the converter this week, not the Bugs Everywhere
repository.

> My overarching purpose in creating a 'rich-root-pack' repository is
> that it's the only solution proposed (in a separate thread) to
> hopefully allow me to rescue branches that already exist in an older
> 'dirstate-with-subtrees' repository.

dirstate-with-subtree and rich-root-pack are model-incompatible with
pack-0.92 repositories.  That is, they contain extra data that a
pack-0.92 repository cannot represent.  As a result, one cannot upgrade,
branch, pull, or merge from a rich-root or subtree repository into a
pack-0.92 repository.

rich-root-pack is not a suitable default format.  I recommend using it
only for projects that were originated in dirstate-with-subtrees format.

This week, I hope to work on a format similar to rich-root-pack that
*will* be a suitable default.  As part of that work, I will be ensuring
that all branches, even weird ones like BE, can be converted into that
format.

> If the result prevents me from working with other Bazaar repositories, I haven't gained much.

There's no particular value in using the same shared repository for
multiple unrelated projects.  In fact, it will be slightly less
efficient than using multiple repositories.

I have multiple repositories, one each for
- - Bazaar and Bzrtools
- - Bugs Everywhere
- - Bundle Buggy
- - Launchpad
- - PyBaz

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIC1OQ0F+nu1YWqI0RAnw3AJ4zrgvrIAdU7IjfW1oUK+xxfiq8VgCdGBok
jhFRjbZID325lQ1b7HKgxKk=
=roH+
-----END PGP SIGNATURE-----