diff options
author | Ryan Mulligan <ryan@ryantm.com> | 2018-08-23 06:19:02 -0700 |
---|---|---|
committer | Ryan Mulligan <ryan@ryantm.com> | 2018-08-23 09:24:44 -0700 |
commit | 5c5baaf17d688151d5c72eb6535ca499ba916fdf (patch) | |
tree | 5a2669877d061648e21c710f7f775339ed3ce2f7 /.github | |
parent | 669d727b5ce5a114bb9c278aba4be083e431c1b5 (diff) |
treewide: remove mailing list references
Diffstat (limited to '.github')
-rw-r--r-- | .github/CONTRIBUTING.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md index 981036bf4a027..576beb18de6a7 100644 --- a/.github/CONTRIBUTING.md +++ b/.github/CONTRIBUTING.md @@ -43,7 +43,7 @@ See the nixpkgs manual for more details on [standard meta-attributes](https://ni ## Writing good commit messages -In addition to writing properly formatted commit messages, it's important to include relevant information so other developers can later understand *why* a change was made. While this information usually can be found by digging code, mailing list archives, pull request discussions or upstream changes, it may require a lot of work. +In addition to writing properly formatted commit messages, it's important to include relevant information so other developers can later understand *why* a change was made. While this information usually can be found by digging code, mailing list/Discourse archives, pull request discussions or upstream changes, it may require a lot of work. For package version upgrades and such a one-line commit message is usually sufficient. |