Supporting nested trees in Bazaar

Registered by Robert Collins

There is desire to split trees into subsections 1. because they contain parts that can vary (e.g. libraries that are also used elsewhere, or are sourced from other locations or projects) and 2. as a performance-enhancing technique. Can we do better than configs? Or can we use configs as an under-the-hood mechanism and provide a transparent UI that lets the tree feel like a single entity ?

Blueprint information

Status:
Started
Approver:
Martin Pool
Priority:
Medium
Drafter:
John A Meinel
Direction:
Approved
Assignee:
Wouter van Heyst
Definition:
Discussion
Series goal:
Accepted for trunk
Implementation:
Good progress
Milestone target:
None
Started by
Aaron Bentley

Related branches

Sprints

Whiteboard

some ongoing discussion 2006-01
(blocked on introduce-root-id)
offloaded from aaron to larstiq

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.