replace references to nmbug.tethera.net with nmbug.notmuchmail.org

[notmuch-wiki] / contributing.mdwn

diff --git a/contributing.mdwn b/contributing.mdwn
index 3729a766cbbc9948401b3c149a15d8c6131227aa..c92853fd90b9108d97c033edcf07217eae4d7bbf 100644 (file)
--- a/contributing.mdwn
+++ b/contributing.mdwn
@@ -9,7 +9,8 @@ but once you get the hang of it, it'll be fun. This page should help
 you get there. DON'T PANIC.
 
 The headlines below act as a checklist. Not all of them apply in all
 you get there. DON'T PANIC.
 
 The headlines below act as a checklist. Not all of them apply in all

-situations; use common sense.
+situations. Use your best judgment, and the Notmuch community will
+help out as needed.

 
 [[!toc levels=2]]
 
 
 [[!toc levels=2]]
 


@@ -105,7 +106,7 @@ in the Notmuch source for further information.
 ## Update the documentation
 
 If you modify or add new features to the Notmuch command-line tools,
 ## Update the documentation
 
 If you modify or add new features to the Notmuch command-line tools,

-you should update the manual pages under the `man` directory of the
+you should update the manual pages under the `doc` directory of the

 Notmuch source.
 
 If you modify or add new features to the Notmuch Emacs UI, you should
 Notmuch source.
 
 If you modify or add new features to the Notmuch Emacs UI, you should


@@ -168,7 +169,7 @@ like email. This applies to patch and bug tracking as well. The
 Notmuch project uses [nmbug](http://notmuchmail.org/nmbug/) for
 tracking. The Notmuch developers will tag your patches too, making
 them show up in the
 Notmuch project uses [nmbug](http://notmuchmail.org/nmbug/) for
 tracking. The Notmuch developers will tag your patches too, making
 them show up in the

-[nmbug status page](http://nmbug.tethera.net/status/), but requesting
+[nmbug status page](http://nmbug.notmuchmail.org/status/), but requesting

 access and tagging your patches yourself will be helpful in the long
 run.
 
 access and tagging your patches yourself will be helpful in the long
 run.
 


@@ -190,14 +191,13 @@ have changed; be sure to rebase your updated changes on top of the
 current master.
 
 Once you have the updated series ready, send it to the mailing list
 current master.
 
 Once you have the updated series ready, send it to the mailing list

-again. It will be helpful for others to use the
-`--subject-prefix="PATCH vN"` option of `git format-patch` or
-`git send-email` to add a version number of the patch series to the
-subject (replacing vN with v2, v3, etc.) Use a cover letter (or, in
-the case of a single patch, the notes after a "---" at the end of the
-commit message) to summarize the main changes since the previous
-version of the patch series. Also include the message-id reference of
-the previous version.
+again. It will be helpful for others to use the `-vN` option of `git
+format-patch` or `git send-email` to add a version number of the patch
+series to the subject (replacing vN with v2, v3, etc.) Use a cover
+letter (or, in the case of a single patch, the notes after a "---" at
+the end of the commit message) to summarize the main changes since the
+previous version of the patch series. Also include the message-id
+reference of the previous version.

 
 Using the `--in-reply-to` option of `git format-patch` or
 `git send-email` to send the patch series as a reply to the earlier
 
 Using the `--in-reply-to` option of `git format-patch` or
 `git send-email` to send the patch series as a reply to the earlier