There are still some places which can be improved by having a dedicated API,
this patch for now make all users of actions dict go through the mergeresult
object API.
Details
Details
- Reviewers
indygreg - Group Reviewers
hg-reviewers - Commits
- rHG5ce63ee1fe3d: merge: replace use of actions dict with mergeresult object
Diff Detail
Diff Detail
- Repository
- rHG Mercurial
- Branch
- default
- Lint
No Linters Available - Unit
No Unit Test Coverage
Event Timeline
Comment Actions
The introduction of sorting here is interesting. I guess we never sorted filenames before performing working directory modifications before? But surely there is sorting happening elsewhere because anything with ui output would need to be sorted to ensure determinism. And surely tests would have caught that.
Also, I remember there being an interplay between parallel workers and filesystem performance. Something about how file I/O is scheduled with respect to discrete directories. @durin42 might know more. (I remember mpm mentioning this when I was poking around with parallel workers and working directory operations several years ago.)
mercurial/merge.py | ||
---|---|---|
1413 | The private attribute access here isn't great. But whatever. |
The private attribute access here isn't great. But whatever.