[RFC] proposed user doc for nested trees

[Aaron Bentley]

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

Aaron Bentley wrote:
> Since the code isn't updating any extra info, updating branch reference
> locations would be a big burden, and you'd need to ensure that it was
> impossible to move a checkout any other way, to avoid breaking the
> user's tree.  That's a very difficult guarantee to provide.
> 
> Whereas, moving checkouts around is a fairly rare event.

What I mean is that moving subtrees within a working tree would be much
more common than moving an entire set of nested trees (composite tree)
around.

I think that means we should optimize for the first one, but it doesn't
mean we can't support the second.  For example, perhaps "bzr switch" in
the root tree could update the branch references.

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

iEYEARECAAYFAkoJhsMACgkQ0F+nu1YWqI2yWQCfQOfpKpj8Wpv/Sa4n3nXgmsq5
aygAn3tnKQrZcEE1zow3PDvSmkthlfiK
=+pKF
-----END PGP SIGNATURE-----