[MERGE] bzr+http:// should always try POSTing to the same location, not lots of child locations.

[Aaron Bentley]

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

Andrew Bennetts wrote:
> I'm not sure what you're referring to with "if we can use an existing transport
> to acquire another BzrDir, that is a performance win" — what cases do we do that
> now that my patch would break?

I mean that if your patch makes it disadvantageous to use clone, we will
also lose potential performance wins.

I'm thinking, in particular, of retrieving nested branches.

Aaron


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

iD8DBQFFwqnW0F+nu1YWqI0RAjGVAKCErUq3UOXZ5tu3ZvINPJAdEFzRsgCeK9dQ
hzTxhFxkj6a7DgSyDJutQFk=
=erW3
-----END PGP SIGNATURE-----