log --long suffers from several apis that require the whole ancestry it uses get_revision_graph to do the merge_sorted call, and it needs to rebuild the revision history of the branch, so it knows what revisions are "mainline". (Some of that is because we used to have cached the mainline, so it was cheaper to ask for it, than to derive it while doing other things.)
log --long suffers from several apis that require the whole ancestry it uses get_revision_graph to do the merge_sorted call, and it needs to rebuild the revision history of the branch, so it knows what revisions are "mainline". (Some of that is because we used to have cached the mainline, so it was cheaper to ask for it, than to derive it while doing other things.)