## Getting started
-1. Install and use notmuch version notmuch 0.9+63~gebd1adc or newer and
+1. Install and use notmuch version **0.10** or newer and
perl module `Pod::Usage` (packaged as `perl-doc` in debian).
The nmbug script is available in `contrib/nmbug`.
-2. The current tag repo can be obtained by:
+2. Make sure your `git version` is **1.7.4** or newer.
- `$ git clone --bare http://nmbug.tethera.net/git/nmbug-tags.git $HOME/.nmbug`
-
- Check that your git is recent enough by entering:
-
- `$ 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).
+ `$ git clone --bare http://nmbug.tethera.net/git/nmbug-tags.git $HOME/.nmbug`
## Using nmbug, simple example
notmuch::moreinfo waiting for feedback from patch proposer
or others
- notmuch::stale The patch no longer applies to master (or in
- rare cases, to release)
+ 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
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