X-Git-Url: https://git.cworth.org/git?a=blobdiff_plain;f=contributing.mdwn;h=11d711bd061abf72aedca1281bd7ad64957bc7ee;hb=56a7ce71e3b208ca556bf0318c407e2156ab25d0;hp=1c8bd5bdd266650a3b3c5fbb403c74101fa969d5;hpb=882d2cdc07b55af79c5354fb2562daee22a62b81;p=obsolete%2Fnotmuch-wiki

diff --git a/contributing.mdwn b/contributing.mdwn
index 1c8bd5b..11d711b 100644
--- a/contributing.mdwn
+++ b/contributing.mdwn
@@ -58,7 +58,7 @@ Each commit should contain one logical change only. The code should
 build and the tests should pass after each commit. Changes to lib,
 cli, emacs, tests, man pages, or news are usually best kept
 separate. Also separate cleanups from functional changes. See the
-Notmuch source history (`git log`) for examples.
+Notmuch source history (**`git log`**) for examples.
 
 For in-depth discussion on the subject, see
 [Software Release Practice HOWTO](http://tldp.org/HOWTO/Software-Release-Practice-HOWTO/) by Eric S. Raymond.
@@ -74,8 +74,8 @@ See also
 on commit guidelines, including commit messages.
 
 It is customary to prefix the subject line with "lib:", "cli:", "emacs:",
-etc. depending on which part of Notmuch the commit is changing. See `git log`
-for examples.
+etc. depending on which part of Notmuch the commit is changing. See
+**`git log`** for examples.
 
 Wrap the lines to about 72 characters.
 
@@ -214,6 +214,12 @@ subject line with "BUG:" or similar. Tag the message as a bug in
 Even better, send a patch adding a "known broken" test to the test suite
 highlighting the issue.
 
+## Update the Notmuch website
+
+Update the Notmuch website, especially if you've landed a commit that
+changes or obsoletes information on the site. It's a wiki; see the
+[[instructions on how to edit the wiki|wikiwriteaccess]].
+
 ## Join the Notmuch IRC channel
 
 Patch review happens on the Notmuch mailing list, but there is plenty of