<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/test, branch debian/0.28.3-1</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=debian%2F0.28.3-1</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=debian%2F0.28.3-1'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2019-03-06T01:46:41Z</updated>
<entry>
<title>lib/string_map: fix return type of string_cmp</title>
<updated>2019-03-06T01:46:41Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2019-03-02T18:10:51Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=e88297c072e6bfbeaedc1287ec695ca37537255e'/>
<id>urn:sha1:e88297c072e6bfbeaedc1287ec695ca37537255e</id>
<content type='text'>
I can't figure out how checking the sign of a bool ever worked. The
following program demonstrates the problem (i.e. for me it prints 1).

 #include &lt;stdio.h&gt;
 #include &lt;stdbool.h&gt;
 int main(int argc, char **argv) {
    bool x;
    x = -1;
    printf("x = %d\n", x);
 }

This seems to be mandated by the C99 standard 6.3.1.2.
</content>
</entry>
<entry>
<title>lib: Add known broken test for string_map binary search.</title>
<updated>2019-03-06T01:46:41Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2019-03-05T18:56:29Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=09595cf577616f657fdfcd235c4e04d91b3c020a'/>
<id>urn:sha1:09595cf577616f657fdfcd235c4e04d91b3c020a</id>
<content type='text'>
Because the string_map functions are not exported, we test via message
properties.
</content>
</entry>
<entry>
<title>emacs: Call `notmuch-mua-send-hook' hooks when sending a message</title>
<updated>2018-09-28T23:22:42Z</updated>
<author>
<name>David Edmondson</name>
<email>dme@dme.org</email>
</author>
<published>2018-09-25T15:09:10Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=e8cb6b2cd63c9ea8a011cb9f672baf04b4c14f7b'/>
<id>urn:sha1:e8cb6b2cd63c9ea8a011cb9f672baf04b4c14f7b</id>
<content type='text'>
Previously any hook functions attached to `notmuch-mua-send-hook' were
ignored.
</content>
</entry>
<entry>
<title>test: Check that `notmuch-mua-send-hook' is called on sending a message</title>
<updated>2018-09-28T23:22:33Z</updated>
<author>
<name>David Edmondson</name>
<email>dme@dme.org</email>
</author>
<published>2018-09-25T15:09:09Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=4e213fe9b4332deb3f11f1dbc71cbdd47a8a1525'/>
<id>urn:sha1:4e213fe9b4332deb3f11f1dbc71cbdd47a8a1525</id>
<content type='text'>
</content>
</entry>
<entry>
<title>test: make regexp test conditional on field processors</title>
<updated>2018-09-14T11:54:20Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2018-09-10T01:36:17Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=c846e15ffee526b70a28b512710968b2db77b724'/>
<id>urn:sha1:c846e15ffee526b70a28b512710968b2db77b724</id>
<content type='text'>
Normally we'd mark it broken, but perversely missing regexp support
actually makes the test pass.
</content>
</entry>
<entry>
<title>test: mark thread subqueries broken without field processors</title>
<updated>2018-09-14T11:54:09Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2018-09-10T01:36:16Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=c6ba5522a5c44312c140b5f61c5a0e011fdf94b2'/>
<id>urn:sha1:c6ba5522a5c44312c140b5f61c5a0e011fdf94b2</id>
<content type='text'>
Currently these tests just fail when notmuch is built against Xapian
1.2.x
</content>
</entry>
<entry>
<title>test: Absolute and relative directory paths.</title>
<updated>2018-09-08T23:19:42Z</updated>
<author>
<name>David Edmondson</name>
<email>dme@dme.org</email>
</author>
<published>2018-09-08T11:49:41Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=4cd5a0a3d5416fd4601f2c14da0845fee5d9ede1'/>
<id>urn:sha1:4cd5a0a3d5416fd4601f2c14da0845fee5d9ede1</id>
<content type='text'>
</content>
</entry>
<entry>
<title>lib: change parent strategy to use In-Reply-To if it looks sane</title>
<updated>2018-09-06T11:07:13Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2018-08-30T11:29:15Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=87934c432c4bee9df09f268a3f05933c59c2caf1'/>
<id>urn:sha1:87934c432c4bee9df09f268a3f05933c59c2caf1</id>
<content type='text'>
As reported by Sean Whitton, there are mailers (in particular the
Debian Bug Tracking System) that have sensible In-Reply-To headers,
but un-useful-for-notmuch References (in particular with the BTS, the
oldest reference is last). I looked at a sample of about 200K
messages, and only about 0.5% these had something other than a single
message-id in In-Reply-To. On this basis, if we see a single
message-id in In-Reply-To, consider that as authoritative.
</content>
</entry>
<entry>
<title>lib: add _notmuch_message_id_parse_strict</title>
<updated>2018-09-06T11:07:13Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2018-08-30T11:29:14Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=b31e44c678bf3bfe81bcc5f159e627551f12700f'/>
<id>urn:sha1:b31e44c678bf3bfe81bcc5f159e627551f12700f</id>
<content type='text'>
The idea is that if a message-id parses with this function, the MUA
generating it was probably sane, and in particular it's probably safe
to use the result as a parent from In-Reply-to.
</content>
</entry>
<entry>
<title>test/thread-replies: mangle In-Reply-To's</title>
<updated>2018-09-06T11:07:13Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2018-08-30T11:29:12Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=35053c2b9af0eb7ce5bd612c642163275490513a'/>
<id>urn:sha1:35053c2b9af0eb7ce5bd612c642163275490513a</id>
<content type='text'>
In a future commit, we will start trusting In-Reply-To's when they
look sane (i.e. a single message-id). Modify these tests so they will
keep passing (i.e. keep choosing References) when that happens.
</content>
</entry>
</feed>
