'bzr pull' could use update_basis_by_delta instead of set_parent_trees
Bug #780548 reported by
John A Meinel
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Confirmed
|
Medium
|
Unassigned |
Bug Description
Currently, bzr pull does an iter_changes() style to merge the new contents into the working tree, but then calls "tree.set_
In a case where there aren't any merges, we should be able to use tree.update_
This currently (bzr-2.4 or bzr-2.3.2) costs us about 15s on a 70k entry dirstate, because of the time it takes to load all the pages of the CHKInventory.
To post a comment you must log in.
Technically a dupe of bug #282941, but I'm leaving this bug open for a moment so that we can investigate why Launchpad's search couldn't find this bug. (The Launchpad bug is bug #780636.) When that bug has been investigated, mark this as a duplicate.