Branching a standalone v6 branch into shared repository

[John Arbash Meinel]

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

We've had this discussion in the past, but I think it is time to bring
it up again, now that we've all lived with bzr.dev for a while.

https://launchpad.net/products/bzr/+bug/37915

For 0.8, we decided that branching a standalone always creates a
standalone v6 branch, because that prevents watershedding.

But the argument that the user has made the conscious decision to create
a local repository, seems to indicate they are okay with the watershed.
We should preserve the format if just going into an empty dir, but
otherwise I think we should upgrade.

Especially now that we've had a whole version of compatibility, and our
weave performance has now gotten much worse.

It would be a whole lot easier for people when they want to upgrade to a
shared knit repository to.

They can just do 'bzr init-repo repo' and then 'bzr branch ../branch-a
repo/branch-a'

Rather than the init + pull song and dance.

John
=:->

PS> I'm doing a summary, but right now doing init + pull from
bzr.dev.as.weaves into a new branch took 40 minutes.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEwVxPJdeBCYSNAAMRAp7pAKCyGYwAU+8X7p7wJqes2edrjHYWKwCglO/t
ZklnWlsrYGMh00m+x5h+0Mk=
=SxN/
-----END PGP SIGNATURE-----