WT.iter_changes(arbitrary_tree) should use chaining
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Confirmed
|
Medium
|
Unassigned |
Bug Description
Right now, bzr has 2 fast iter_changes paths. RevTree.
The dirstate layout is not similar to how the data is stored in the repository (dirstate is ordered by path, repo is ordered ~by file-id.).
However, we should be able to composite 2 iter_changes output together. So doing "WT.iter_
WT.iter_
tags: | added: check-for-breezy |
This would be relevant for "bzr revert/status/diff -r -10". I'm not sure if that is common enough that we should focus on it, though. Implementing chained iter_changes() is a fair amount of logic, and needs very careful edge-case handling.