The config override seems to have a much greater scope than it needed
to. I *think* it's only relevant in the while merging files. The
rebase step also cares about the merge tool, but we seem to be
explicitly passing it to rebase (around line 755).
Details
Details
- Reviewers
- None
- Group Reviewers
hg-reviewers - Commits
- rHG7932be8b0559: shelve: reduce scope of merge tool config override
Diff Detail
Diff Detail
- Repository
- rHG Mercurial
- Lint
Lint Skipped - Unit
Unit Tests Skipped
Event Timeline
Comment Actions
+ shelvectx = _rebaserestoredcommit(ui, repo, opts, tr, oldtiprev,
+ basename, pctx, tmpwctx,
+ shelvectx, branchtorestore,
+ activebookmark)overrides = {('ui', 'forcemerge'): opts.get('tool', '')} with ui.configoverride(overrides, 'unshelve'):
Maybe I'm wrong, but doesn't rebase do merge?
Comment Actions
Correct, but we seem to be passing the tool explicitly to the rebase command on line 755. I had checked this before, and should have mentioned it in the commit message. Sorry.
Comment Actions
> > + shelvectx = _rebaserestoredcommit(ui, repo, opts, tr, oldtiprev, > > + basename, pctx, tmpwctx, > > + shelvectx, branchtorestore, > > + activebookmark) > > > > overrides = {('ui', 'forcemerge'): opts.get('tool', '')} > > with ui.configoverride(overrides, 'unshelve'): > > Maybe I'm wrong, but doesn't rebase do merge? Correct, but we seem to be passing the tool explicitly to the rebase command on line 755.
Right. Queued this, thanks.