view CONTRIBUTING @ 40073:e92454e69dc3

narrow: introduce a config option to check if narrow is enabled or not

This patch introduces a new config option experimental.narrow which is set to
False by default and set to True by the narrow extension.

While moving narrow related logic into core, we need to know at places whether
narrow extension is enabled or not. Checking the list of extension enabled is
one solution but once narrow is inbuilt, we will definitely want a config option
to check whether narrow is turned on or not.

So this patch introduces a config option, which will evolve to the main point to
turn narrow capability on and off once all the narrow is in core.

Differential Revision: https://phab.mercurial-scm.org/D4889

Our full contribution guidelines are in our wiki, please see:

https://www.mercurial-scm.org/wiki/ContributingChanges

If you just want a checklist to follow, you can go straight to

https://www.mercurial-scm.org/wiki/ContributingChanges#Submission_checklist

If you can't run the entire testsuite for some reason (it can be
difficult on Windows), please at least run `contrib/check-code.py` on
any files you've modified and run `python contrib/check-commit` on any
commits you've made (for example, `python contrib/check-commit
273ce12ad8f1` will report some style violations on a very old commit).