summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDavid Edmondson <dme@dme.org>2011-12-21 19:45:44 +0000
committerDavid Edmondson <dme@dme.org>2011-12-21 19:45:44 +0000
commit73be4fe07c5a3d57bc441115383cea0dcd49921f (patch)
treeca2d28053e01b3b66b9eb63834400b966e392fd7
parent8687059c5b0c5fedd7c2160d74d9087c99d86763 (diff)
More minor tidying of the nmbug description.
-rw-r--r--nmbug.mdwn11
1 files changed, 5 insertions, 6 deletions
diff --git a/nmbug.mdwn b/nmbug.mdwn
index 12c25ca..999b781 100644
--- a/nmbug.mdwn
+++ b/nmbug.mdwn
@@ -132,30 +132,29 @@ These patches are more comments and suggestions.
notmuch::$n this patch should be considered for
release $n
-## TRACKING the patch queue
+## Tracking the patch queue
I (David Bremner) use the following search (in my case as a saved
-search in emacs).
+search in emacs):
tag:notmuch::patch and not tag:notmuch::pushed and \
not tag:notmuch::obsolete and not tag:notmuch::wip \
and not tag:notmuch::moreinfo and not tag:notmuch::contrib
You might or might not want as many exclusions. Another interesting
-search is
+search is:
tag:notmuch::reviewed and not tag:notmuch::pushed
## Design notes
-### Disk format.
+### Disk format
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
-
+them, the tree looks something like:
tags/878waiwi0f.wl%25james@hackervisions.org/
tags/878waiwi0f.wl%25james@hackervisions.org/emacs