Future bzr features: split file tracking and type-specific merging

[Andrew Lambe]

Are there any plans for bzr to support splitting of versioned files?
For instance, if I write a long bash script and later find that I want
to reuse a portion of it in another script, I would split code to reuse
into another file.
Currently with bzr I would now have a modified file with a bunch of
deleted code and an added file with the old code in it, but bzr has no
association between the two files or the code they contain.
>From what I understand GIT has features to support this kind of
tracking.
Will bzr?

Second, are there any plans for bzr to support intelligent
type-specific merging, such as preserving functions in C code or tree
structures in XML?
The best way to do this for each of a multitude of languages, file
formats, and syntaxes is of course a much broader topic and feat than
bzr is going for (right now ;), but bzr could support the infrastructure
needed.
There are essentially two parts to this: language/file format detection
and type-specific merging.
For the first part, plugins could aid the user in detecting or
specifying the file type to bzr, but is bzr being designed to allow
arbitrary file type metadata to be kept about each versioned file?
For the second part, is bzr being designed to allow different merging
behavior (supported by plugins) based on those file types?



-- 

Andrew Lambe
Systems Programmer
Information Technology
Oral Roberts University
Tulsa, Oklahoma