We still need to linearize the revisions in some cases, introduce an explicit
linear sorting before changing back the default order.
Details
- Reviewers
indygreg - Group Reviewers
hg-reviewers - Commits
- rHG256b1f0c24e8: changegroup: introduce an explicit linear sorting
Diff Detail
- Repository
- rHG Mercurial
- Lint
Automatic diff as part of commit; lint not applicable. - Unit
Automatic diff as part of commit; unit tests not applicable.
Event Timeline
We still need to linearize the revisions in some cases, introduce an explicit `linear` sorting before changing back the default order.
I'm a little confused about this. We do introduce nodesorder='linear', but
there seems no user of that option. Are there unsent patches?
The message should have said We **may** still need to. There is no user of that option yet so we can drop it.
I think we should at least keep the option in storageutil.emitrevision so we can experiment around doing a DAG sort for various operations, @indygreg seems to have some perf improvements on the firefox repo with it
> > We still need to linearize the revisions in some cases, introduce an explicit > > `linear` sorting before changing back the default order. > > I'm a little confused about this. We do introduce `nodesorder='linear'`, but > there seems no user of that option. Are there unsent patches? The message should have said `We **may** still need to`. There is no user of that option yet so we can drop it. I think we should at least keep the option in `storageutil.emitrevision` so we can experiment around doing a DAG sort for various operations, @indygreg seems to have some perf improvements on the firefox repo with it
Got it, thanks. The series looks good, but I leave it to indygreg as he
might have a better idea.
Yeah, I'm OK with this. There is tons of room to experiment with different ordering techniques - including making it end-user configurable. Having this code in place is a step in the right direction.