From patchwork Fri Oct 13 19:59:18 2017 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: D1062: tweakdefaults: make experimental.updatecheck be `noconflict` From: phabricator X-Patchwork-Id: 24855 Message-Id: To: mercurial-devel@mercurial-scm.org Date: Fri, 13 Oct 2017 19:59:18 +0000 durin42 created this revision. Herald added a subscriber: mercurial-devel. Herald added a reviewer: hg-reviewers. REVISION SUMMARY This is the second-safest option we have to offer in `updatecheck`, with `abort` being the safest and `linear` being the default. At the sprint we discussed how much `none` and `linear` make us all uncomfortable, and how we'd like to move the default behavior if we can. I'm not sure we can get away with actually changing the out of the box default behavior, but we can at *least* do this. Open question: should we move this config knob to someplace other than [experimental] before we put it in tweakdefaults? I think we should. In that case, where does it move? commands.update.check? REPOSITORY rHG Mercurial REVISION DETAIL https://phab.mercurial-scm.org/D1062 AFFECTED FILES mercurial/ui.py CHANGE DETAILS To: durin42, #hg-reviewers Cc: mercurial-devel diff --git a/mercurial/ui.py b/mercurial/ui.py --- a/mercurial/ui.py +++ b/mercurial/ui.py @@ -54,6 +54,9 @@ # Make `hg status` emit cwd-relative paths by default. status.relative = yes +[experimental] +updatecheck=noconflict + [diff] git = 1 """