<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/contrib/nmbug, branch 0.15</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=0.15</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=0.15'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2012-10-24T21:54:26Z</updated>
<entry>
<title>contrib/nmbug/nmbug-status: combine thread messages</title>
<updated>2012-10-24T21:54:26Z</updated>
<author>
<name>Tomi Ollila</name>
<email>tomi.ollila@iki.fi</email>
</author>
<published>2012-10-24T06:59:59Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=02cafc84b4540cd0fb878121dcb3551b4ecd9fd1'/>
<id>urn:sha1:02cafc84b4540cd0fb878121dcb3551b4ecd9fd1</id>
<content type='text'>
Newer patch email containing In-Reply-To: to an email sent some time ago
(i.e. to a "thread") was not visible in that "thread" in patch view when
another patch "thread" was submitted in between. This change collects
all messages in every (notmuch-created) thread together before printing
all these threads out in a patch view.

Thanks to Ethan Glasser-Camp for initial review and suggestions with
code examples.
</content>
</entry>
<entry>
<title>contrib/nmbug/nmbug-status: added table of views</title>
<updated>2012-10-24T21:53:58Z</updated>
<author>
<name>Tomi Ollila</name>
<email>tomi.ollila@iki.fi</email>
</author>
<published>2012-10-24T06:59:58Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=d1e09413502f9affc4fd72b5624967c36606526b'/>
<id>urn:sha1:d1e09413502f9affc4fd72b5624967c36606526b</id>
<content type='text'>
In latest configuration quite a few long views were added to the
Notmuch Patches page. To ease navigating to the views a 'Views'
section was added to the beginning of page containing hyperlink
to every view.
</content>
</entry>
<entry>
<title>contrib/nmbug/nmbug-status: if realname empty, use part of mailaddr</title>
<updated>2012-09-02T01:58:49Z</updated>
<author>
<name>Tomi Ollila</name>
<email>tomi.ollila@iki.fi</email>
</author>
<published>2012-08-24T17:29:21Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=6b47e2223d1d21cde34d2f53ede2209f932e7c09'/>
<id>urn:sha1:6b47e2223d1d21cde34d2f53ede2209f932e7c09</id>
<content type='text'>
When the From: field in patch email does not contain 'realname'
field, the patch listing does not show anything as patch sender.
In this case use the part before '@' in mail address as the sender
identification in patch listing.
</content>
</entry>
<entry>
<title>contib/nmbug/nmbug-status: leftover whitespaces, indentation &amp; quoting</title>
<updated>2012-07-12T22:02:09Z</updated>
<author>
<name>Tomi Ollila</name>
<email>tomi.ollila@iki.fi</email>
</author>
<published>2012-07-11T09:10:05Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=898128b9f449431886420710b571eacebbb6dd4b'/>
<id>urn:sha1:898128b9f449431886420710b571eacebbb6dd4b</id>
<content type='text'>
The initial nmbug-status was pretty consistent in it's whitespacing
but a few lines had some leftover slips. Those are now "corrected".

Also, most of the code used ' as quoting char. As in Python one can
use ' and " interchangeably some code used " instead of '. However
the usage of those were inconsistent. Now all quotes that python
parses are ':s (only quoted content uses ":s).

No functional changes.
</content>
</entry>
<entry>
<title>contrib/nmbug/ nmbug-status: restored out['subject']... block level</title>
<updated>2012-07-12T22:01:42Z</updated>
<author>
<name>Tomi Ollila</name>
<email>tomi.ollila@iki.fi</email>
</author>
<published>2012-07-11T09:10:04Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=620092001e58cb092634a0063758f3e4c05c75fa'/>
<id>urn:sha1:620092001e58cb092634a0063758f3e4c05c75fa</id>
<content type='text'>
In reformatting the line 111 accidentally indented to one indentation
level too much (happens easily when interactively indenting python
code using emacs). The line now has 4 spacess less indentation, thus
restoring it to the block level it belongs.
</content>
</entry>
<entry>
<title>contrib/nmbug: add nmbug-status script</title>
<updated>2012-07-10T21:43:32Z</updated>
<author>
<name>David Bremner</name>
<email>bremner@debian.org</email>
</author>
<published>2012-07-07T19:29:38Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=3e5fb88f11359b0c3d43eb06f105ef42e63d31b5'/>
<id>urn:sha1:3e5fb88f11359b0c3d43eb06f105ef42e63d31b5</id>
<content type='text'>
This is (almost) the same script as has been used for
http://nmbug.tethera.net/status for a while now. The only change is
that the configuration is not hardcoded anymore. By default the config
is fetched from a special branch in the nmbug repo that contains only
config info. The idea is that push access to this branch can be
restricted a bit more than the tags, since it will change the
appearence of the web pages.
</content>
</entry>
<entry>
<title>contrib/nmbug: make nmbug a subdirectory</title>
<updated>2012-07-09T22:16:26Z</updated>
<author>
<name>David Bremner</name>
<email>bremner@debian.org</email>
</author>
<published>2012-07-07T18:56:06Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=0d6d5fb8126699cbb1f675f5915534bb430a80fc'/>
<id>urn:sha1:0d6d5fb8126699cbb1f675f5915534bb430a80fc</id>
<content type='text'>
I want to ship the status tool here as well, along with a sample
config file.
</content>
</entry>
<entry>
<title>nmbug: check whether every forked process exit with (non)zero value</title>
<updated>2012-06-03T16:45:28Z</updated>
<author>
<name>Tomi Ollila</name>
<email>tomi.ollila@iki.fi</email>
</author>
<published>2012-04-01T18:28:42Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=a114ac8b77c683fafb350e3f3e07fdbbcf4edd3f'/>
<id>urn:sha1:a114ac8b77c683fafb350e3f3e07fdbbcf4edd3f</id>
<content type='text'>
If any of the forked process exits with nonzero value, terminate
current operation -- nonzero exit value indicates failure and
then there is no point continuing.
</content>
</entry>
<entry>
<title>contrib/nmbug: new script for sharing tags with a given prefix.</title>
<updated>2011-11-13T01:24:25Z</updated>
<author>
<name>David Bremner</name>
<email>bremner@debian.org</email>
</author>
<published>2011-11-13T01:24:25Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=ebd1adc55bcd0f484984bb87f0ea5c0e7091d062'/>
<id>urn:sha1:ebd1adc55bcd0f484984bb87f0ea5c0e7091d062</id>
<content type='text'>
The main idea is consider the notmuch database as analogous to the
work-tree. A bare git repo is maintained in the users home directory,
with a tree of the form tags/$message-id/$tag

Like notmuch and git, we have a set of subcommnds, mainly modelled on
git.

Implementation wise, the heavy lifting is in the following functions.

   commit	xapian -&gt; git
   checkout	git -&gt; xapian
   merge	fetched git + git -&gt; xapian
   status	find differences between xapian, git, and remote git.

The central implementation trick, from an idea I think due to
tomprince on IRC is manipulate the git index directly from the xapian
tag information.  The merge routine is still done using a temporary
checkout as I wasn't able to get it working with the index only.

There are also some convenience wrappers around git commands, like "fetch"
that essential just set GIT_DIR in the environment.

In order to encode tags (viewed as octet sequences) into filenames,
we whitelist a smallish set of characters and %hex escape anything outside.

The prefix is omitted in git, which lets one save and restore to
different prefixes (although this is only lightly tested).

Thanks to Tomi Ollila for a huge amount of feedback and patches while
putting this together.
</content>
</entry>
</feed>
