point list archives to the nmweb frontend

[notmuch-wiki] / contributing.mdwn

diff --git a/contributing.mdwn b/contributing.mdwn
index b5e6cf9b7085e4c610299844754b51ea53bbe4a0..34b7eb6e7b48785de64884b93abc27b38d7d1bcf 100644 (file)
--- a/contributing.mdwn
+++ b/contributing.mdwn
@@ -158,7 +158,7 @@ If you are submitting a non-trivial set of patches, or if there's any
 extra information you want to share that is not really part of the
 commit messages, it is advisable to write a cover letter to give an
 overview of your work. See the
-[Notmuch mailing list archives](https://notmuchmail.org/pipermail/notmuch/)
+[Notmuch mailing list archives](https://nmbug.notmuchmail.org/nmweb/)
 for examples. Use the `--cover-letter` option of `git format-patch`,
 or `--compose` option of `git send-email`.
 
@@ -180,7 +180,7 @@ usually by one or two developers, depending on the impact of the
 changes. You are expected to follow up on the review comments you
 receive, either by discussing the comments and the code, or modifying
 your patches. Again, see the [Notmuch mailing list
-archives](https://notmuchmail.org/pipermail/notmuch/) for examples.
+archives](https://nmbug.notmuchmail.org/nmweb) for examples.
 
 ## Send another round addressing review comments