Nested Trees and History after Splitting

[Gioele Barabucci]

A. S. Budden wrote:
> This is because the 'split' project has taken all of
> the history of the parent project, including the history of all the
> files that have absolutely nothing to do with the library module.
The solution to your problem is to use bzr fast-export and
bzr fast-import -i. This older post of mine could help you: 
http://article.gmane.org/gmane.comp.version-control.bazaar-ng.general/60300

About the rest of your message: what you are requesting/suggesting/proposal 
is similar to what I proposed in the "Things to remove for 2.0" thread [1].

I think this is an example of how much people are confused by a 'split' 
command that does not split directories into standalone branches but just 
hides directories.

I understand that history-rewriting is bad because it prevents merging, but 
in this case people no longer care about merging, they just want a little 
branch with only a limited part of history.

Could you, bzr developers, please reconsider the current semantic of split? 
At least, could a history-rewriting version of split be provided?

[1] http://thread.gmane.org/gmane.comp.version-control.bazaar-
ng.general/60289/focus=60293

-- 
Gioele Barabucci <gioele at svario.it>