thread-based email index, search, and tagging https://git.notmuchmail.org/git/notmuch/atom?h=0.17 2013-12-22T12:44:44Z 2013-12-22T12:44:44Z David Bremner david@tethera.net 2013-12-14T14:39:54Z urn:sha1:513a36d105995c327c23fec5f60ea70c65b986dd Most of the tests previously using emacs_deliver_message do not use the actual transmitted message, so we replace it with a simpler (and presumably more reliable function) that only saves (and indexes) an fcc copy of the message. 2013-11-09T00:43:29Z Austin Clements amdragon@MIT.EDU 2013-10-24T15:19:08Z urn:sha1:abeac48522ded66e2f0e9aae704482355cb46e6a These queries will match exactly the set of messages currently in the thread, even if more messages later arrive. Two queries are provided: one for matched messages and one for unmatched messages. This can be used to fix race conditions with tagging threads from search results. While tagging based on a thread: query can affect messages that arrived after the search, tagging based on stable queries affects only the messages the user was shown in the search UI. Since we want clients to be able to depend on the presence of these queries, this ushers in schema version 2. 2012-12-17T13:11:57Z Peter Wang novalazy@gmail.com 2012-12-15T03:06:45Z urn:sha1:732f50a20aac461101986fafec95771c8a686ebe Update tests to expect content-length and content-transfer-encoding fields in show --format=json output, for leaf parts with omitted body content. 2012-12-08T13:30:46Z Peter Feigl craven@gmx.net 2012-12-06T21:12:14Z urn:sha1:76271e098c6f2b3cc0958bd9996aa7bb9c753f34 Add basic tests, the same as for json, for the S-Expression output format.