Trying out nested trees

[Jelmer Vernooij]

Hi Aaron,

I thought I'd give the current nested trees support a spin and noticed
the following issues that I think aren't covered by your current
patches. Overall, I really like how easy it is to work with subtrees;
it's much more intuitive than svn externals or git submodules IMSNHO.

Adding a subtree without changing that subtree itself gives the
following output during commit:

Committing to:
/home/jelmer/tmp/subtree/                                      
Committing to:
/home/jelmer/tmp/subtree/specimen/                             
aborting commit write group: PointlessCommit(No changes to commit)
added specimen
Committed revision 1.

The PointlessCommit error for the subtree is a bit confusing.

"bzr ls" also seems to not handle tree-references inventory entries yet
(bzr: ERROR: unknown kind 'tree-reference')

Push seems to error out somehow trying to push the branch with the subtree:

ganieda:~/tmp/subtree% bzr.dev push ../subtree2
bzr: ERROR: Not a branch: "/home/jelmer/tmp/subtree2/specimen/".

"bzr add <existing-branch>" is a noop, e.g. if foo is a branch:

$ bzr add foo
$ bzr st
unknown:
  foo

I think this should probably warn the user that they want to use "bzr
join --reference".

Cheers,

Jelmer