[MERGE][0.15] Hide commands for nested trees.

[Aaron Bentley]

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

Robert Collins wrote:
> On Tue, 2007-03-13 at 12:07 +1100, Martin Pool wrote:
>> On 13/03/07, Aaron Bentley <aaron.bentley at utoronto.ca> wrote:
>  Even with
>>> "nested-tree polish update 1" (which hasn't even made bzr.dev), they
>>> aren't even supported by basic commands like 'status', 'pull' and 'revert'.
> 
> What do you mean here? Will they break commonly? Or do you mean 'status
> wont recurse into subtrees, and neither will pull' ?

Mostly, I mean that "status" and "pull" (and others) won't recurse into
subtrees.

Also, revert can't handle moving the root, which is what happens any
time you split or join.

> I'd rather we dont have a new format here, I think having a new feature
> which is available by choice (must explicitly upgrade to it), is fine.
> nested-trees are already implicitly disabled for vanilla knit
> repositories.

That is okay with me, I just think it makes sense to hide the commands
for now.

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

iD8DBQFF9jM/0F+nu1YWqI0RAjmKAJ9h3rVOb7XGR1QYHLYyjrEV0LBSGwCePXZu
HgQaJY5aNGxcVC6E+R9mc/g=
=itvu
-----END PGP SIGNATURE-----