Mercurial > hg
view CONTRIBUTING @ 34923:a6a322193a02 stable
setup: filter out devel-warn messages from system hg
If we're going to use the user's installed and configured hg command
(which we do since 8b20338b989e), we should prevent devel-warn messages
from interfering with locating it.
author | Kevin Bullock <kbullock+mercurial@ringworld.org> |
---|---|
date | Mon, 23 Oct 2017 22:13:59 -0500 |
parents | a492610a2fc1 |
children |
line wrap: on
line source
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).