Merge lp://staging/~jameinel/bzr-fastimport/fastimport-kg into lp://staging/bzr-fastimport
Proposed by
John A Meinel
Status: | Merged |
---|---|
Approved by: | Ian Clatworthy |
Approved revision: | not available |
Merged at revision: | not available |
Proposed branch: | lp://staging/~jameinel/bzr-fastimport/fastimport-kg |
Merge into: | lp://staging/bzr-fastimport |
Prerequisite: | lp://staging/~jameinel/bzr-fastimport/less-sticky |
Diff against target: |
71 lines (+38/-2) 1 file modified
revision_store.py (+38/-2) |
To merge this branch: | bzr merge lp://staging/~jameinel/bzr-fastimport/fastimport-kg |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Ian Clatworthy | Approve | ||
Review via email:
|
To post a comment you must log in.
This is also dependent on /code.edge. launchpad. net/~jameinel/ bzr/2.1. 0b4-kg- add-node/ +merge/ 15457
https:/
However the code should be compatible either way (by using a getattr() check).
Anyway, this replaces the graph heads functionality of the commit builder by a KnownGraph implementation, which should be a lot faster. Though it only comes into play when we have an actual merge ancestry, which isn't a lot of xserver (most of it is linear).
The main downside is that it seems to actually generate a different number of file texts than the old code. Which surprises me enough that I think it should be looked at.