thread-based email index, search, and tagging https://git.notmuchmail.org/git/notmuch/atom?h=master 2013-02-16T11:54:33Z 2013-02-16T11:54:33Z David Bremner bremner@debian.org 2013-02-16T11:54:33Z urn:sha1:41a29a84721235e33aff23bf6ef61b9ffdded2ef There seems to be consensus to use presence in contrib as documentation of limited support by the notmuch developers; in fact nmbug is pretty integrated into our current development process, so devel seems more appropriate. 2013-02-14T11:57:05Z Jani Nikula jani@nikula.org 2013-02-09T22:49:00Z urn:sha1:a03769db17fe5e2ff15a27391086387d1bfe37e7 nmbug pull only merges upstream master, but nmbug push tries to push all local branches. The asymmetry results in conflicts whenever there have been changes in the config branch in the origin: $ nmbug push To nmbug@nmbug.tethera.net:nmbug-tags ! [rejected] config -> config (non-fast-forward) error: failed to push some refs to 'nmbug@nmbug.tethera.net:nmbug-tags' hint: Updates were rejected because a pushed branch tip is behind its remote hint: counterpart. If you did not intend to push that branch, you may want to hint: specify branches to push or set the 'push.default' configuration hint: variable to 'current' or 'upstream' to push only the current branch. 'git push origin' exited with nonzero value To fix this, only push the master branch on nmbug push. Any config changes need to be done manually via git anyway. 2012-10-24T21:54:26Z Tomi Ollila tomi.ollila@iki.fi 2012-10-24T06:59:59Z urn:sha1:02cafc84b4540cd0fb878121dcb3551b4ecd9fd1 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. 2012-10-24T21:53:58Z Tomi Ollila tomi.ollila@iki.fi 2012-10-24T06:59:58Z urn:sha1:d1e09413502f9affc4fd72b5624967c36606526b 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. 2012-09-02T01:58:49Z Tomi Ollila tomi.ollila@iki.fi 2012-08-24T17:29:21Z urn:sha1:6b47e2223d1d21cde34d2f53ede2209f932e7c09 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. 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.