thread-based email index, search, and tagging https://git.notmuchmail.org/git/notmuch/atom?h=0.14 2012-07-12T22:02:09Z 2012-07-12T22:02:09Z Tomi Ollila tomi.ollila@iki.fi 2012-07-11T09:10:05Z urn:sha1:898128b9f449431886420710b571eacebbb6dd4b 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. 2012-07-12T22:01:42Z Tomi Ollila tomi.ollila@iki.fi 2012-07-11T09:10:04Z urn:sha1:620092001e58cb092634a0063758f3e4c05c75fa 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. 2012-07-10T21:43:32Z David Bremner bremner@debian.org 2012-07-07T19:29:38Z urn:sha1:3e5fb88f11359b0c3d43eb06f105ef42e63d31b5 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. 2012-07-09T22:16:26Z David Bremner bremner@debian.org 2012-07-07T18:56:06Z urn:sha1:0d6d5fb8126699cbb1f675f5915534bb430a80fc I want to ship the status tool here as well, along with a sample config file. 2012-06-03T16:45:28Z Tomi Ollila tomi.ollila@iki.fi 2012-04-01T18:28:42Z urn:sha1:a114ac8b77c683fafb350e3f3e07fdbbcf4edd3f 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. 2011-11-13T01:24:25Z David Bremner bremner@debian.org 2011-11-13T01:24:25Z urn:sha1:ebd1adc55bcd0f484984bb87f0ea5c0e7091d062 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 -> git checkout git -> xapian merge fetched git + git -> 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.