'bzr pull' uses generic iter_changes api
Bug #780677 reported by
John A Meinel
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Fix Released
|
Medium
|
John A Meinel |
Bug Description
I'm doing some profiling of stuff like pull in a large tree (70k entries). It looks like it is falling back to the generic InterTree for iter_changes. My guess is because pull is probably using the DirStateRevisio
Related branches
lp:~jameinel/bzr/2.4-pull-iter-changes-780677
- Andrew Bennetts: Approve
-
Diff: 56 lines (+19/-5)3 files modifiedbzrlib/workingtree.py (+5/-0)
doc/en/release-notes/bzr-2.4.txt (+8/-0)
doc/en/whats-new/whats-new-in-2.4.txt (+6/-5)
Changed in bzr: | |
assignee: | nobody → John A Meinel (jameinel) |
status: | Confirmed → In Progress |
Changed in bzr: | |
milestone: | none → 2.4b3 |
status: | In Progress → Fix Released |
To post a comment you must log in.
I'm pretty sure this also affects 'bzr update', but haven't tested it specifically.