Drop reference to notmuch-commits mailing list.

[notmuch-wiki] / contributing.mdwn

diff --git a/contributing.mdwn b/contributing.mdwn
index 2fca0ca5d180cc733ac250b0a01a909e8f7c932b..b5e6cf9b7085e4c610299844754b51ea53bbe4a0 100644 (file)
--- a/contributing.mdwn
+++ b/contributing.mdwn
@@ -19,7 +19,7 @@ help out as needed.
 The Notmuch source code is maintained in [git](http://git-scm.com/). Get the
 source code using:
 
-        git clone git://notmuchmail.org/git/notmuch
+        git clone https://git.notmuchmail.org/git/notmuch
 
 This guide assumes a working knowledge of git. There are plenty of resources
 available on git, such as [Pro Git](http://git-scm.com/book) and the git man
@@ -128,7 +128,7 @@ afterwards.
 ## Subscribe to the Notmuch mailing list
 
 While strictly not required, it is advisable to subscribe to the
-[Notmuch mailing list](https://notmuchmail.org/mailman/listinfo/notmuch)
+[Notmuch mailing list](https://nmbug.notmuchmail.org/list/)
 before submitting patches.
 
 ## Send your patches to the mailing list
@@ -169,7 +169,7 @@ like email. This applies to patch and bug tracking as well. The
 Notmuch project uses [nmbug](https://notmuchmail.org/nmbug/) for
 tracking. The Notmuch developers will tag your patches too, making
 them show up in the
-[nmbug status page](http://nmbug.notmuchmail.org/status/), but requesting
+[nmbug status page](https://nmbug.notmuchmail.org/status/), but requesting
 access and tagging your patches yourself will be helpful in the long
 run.