Split/Join feature

[Nicholas Allen]

> This is part of the new subtree support that has just landed with
> dirstate in bzr.dev. Its quite possible we will disable these commands
> for 0.15, as the userspace for subtrees is rather... raw. That said, it
> splits a tree into two trees, e.g. if you have a library you want to
> turn into a separate project, split is the command to do that.
>
> -Rob
>   
Does that mean if I split a project in 2 but then make changes in both 
of them I only need to commit once to commit to both of them? What does 
it mean to have subtree support? I think it sounds like a great feature 
but I don't understand the full potential of it. It would be nice if 
there was at least some documentation showing use cases and explaining a 
bit more about it. Otherwise this great feature will land and most 
people won't get excited about it because they can't easily see how it 
would be of benefit to them or how to use it. I know the bzr 
documentation is not in a great shape but when a major new feature lands 
would it not make sense that at least a file in the docs dir is created 
for it before it can be released (or even merged to trunk)? Just a 
thought....

Cheers,

Nick