X-Git-Url: https://git.cworth.org/git?a=blobdiff_plain;f=nmbug.mdwn;h=64e73313245d16f3078d0b97cde3e352450ae3c0;hb=20f029ccd9d29a7cd9b7414488f9c278fba8eb30;hp=6431ee9c68397c5c515bba43af5aec633687cac7;hpb=eebc9595c7eaeadf2a5a23bbd4c5990c37bce2b0;p=notmuch-wiki

diff --git a/nmbug.mdwn b/nmbug.mdwn
index 6431ee9..64e7331 100644
--- a/nmbug.mdwn
+++ b/nmbug.mdwn
@@ -1,3 +1,4 @@
+[[!img notmuch-logo.png alt="Notmuch logo" class="left"]]
 # Experimental Tag Sharing / Pseudo-Bug-Tracking for/with notmuch
 
 ## Web View
@@ -6,20 +7,18 @@ There is a dump of (some views of) the nmbug [[status|http://nmbug.tethera.net/s
 
 ## Getting started
 
-1. Install and use notmuch version notmuch 0.9+63~gebd1adc or newer and
-   perl module `Pod::Usage` (packaged as `perl-doc` in debian).
-
-   The nmbug script is available in `contrib/nmbug`.
+0. Make sure that the whole notmuch@notmuchmail.org mailing list archive is available in your email database.
 
-2. The current tag repo can be obtained by:
+1. Install and use nmbug from notmuch version **0.18** or newer and
+   perl module `Pod::Usage` (packaged as `perl-doc` in debian).
 
-   `$ git clone --bare http://nmbug.tethera.net/git/nmbug-tags.git $HOME/.nmbug`
+   The nmbug script is available in [devel/nmbug][nmbug].
 
-   Check that your git is recent enough by entering:
+2. Make sure your `git version` is **1.7.4** or newer. 
 
-   `$ git --git-dir=$HOME/.nmbug fetch`
+3. Enter the following command to obtain the current tag repository:
 
-   If you get failures then you need to update your git (as well).
+   `$ nmbug clone http://nmbug.tethera.net/git/nmbug-tags.git`
 
 ## Using nmbug, simple example
 
@@ -112,6 +111,12 @@ Sometimes the process stalls, and patches get tagged:
                                 or others
     notmuch::stale              The patch no longer applies to master (or in
                                 rare cases, to release)
+
+Note that these tags typically apply to whole series of patches; it
+doesn't usually make sense to apply patches later in the series before
+earlier ones. So a patch may be tagged `moreinfo` or `stale` only
+because a predecessor patch is.
+
 ### Bug tracking tag
 
 So far we are just tagging certain messages as bug reports, meaning
@@ -147,7 +152,10 @@ search in emacs):
 You might or might not want as many exclusions.  Another interesting
 search is:
 
-    tag:notmuch::reviewed and not tag:notmuch::pushed
+    tag:notmuch::patch and not tag:notmuch::needs-review and not \
+        tag:notmuch::pushed and not tag:notmuch::obsolete and not \
+            tag:notmuch::wontfix and not tag:notmuch::moreinfo and not \
+                tag:notmuch::stale and not tag:notmuch::wip
 
 See the [[status|http://nmbug.tethera.net/status]] page for more
 example searches.
@@ -158,8 +166,8 @@ example searches.
 
 The tags are stored in a bare-repo, which means they are not obviously
 visible. There is an `nmbug archive` command analogous to `git
-archive` Tags are represented as empty files in the tree; if you extra
-them, the tree looks something like:
+archive` Tags are represented as empty files in the tree; if you
+extract them, the tree looks something like:
 
     tags/878waiwi0f.wl%25james@hackervisions.org/
     tags/878waiwi0f.wl%25james@hackervisions.org/emacs
@@ -175,3 +183,5 @@ The `%25` represents hex code for a character that cannot be used directly
 
 - Currently the parser of nmbug (like that of notmuch restore) assumes
   that there are no spaces in message-ids.
+
+[nmbug]: http://git.notmuchmail.org/git/notmuch/blob/HEAD:/devel/nmbug/nmbug