scmutil.cleanupnodes() schedules stripping to be done after the
current transaction, so we can safely run it within the
transaction. This also means that the phase will be updated within the
transaction, which I believe means that the initial (possibly
incorrect) phase will not visible.
Details
Details
- Reviewers
- None
- Group Reviewers
hg-reviewers - Commits
- rHGc6a5009ed04a: absorb: run cleanupnodes() within transaction also when not using obsmarkers
Diff Detail
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.