<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/test, branch 0.26.2</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=0.26.2</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=0.26.2'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2018-04-24T02:00:20Z</updated>
<entry>
<title>lib: choose oldest message when breaking reference loops</title>
<updated>2018-04-24T02:00:20Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2018-04-20T14:59:48Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=491b1f4b4082bee18418942846ec6508856be7b4'/>
<id>urn:sha1:491b1f4b4082bee18418942846ec6508856be7b4</id>
<content type='text'>
This preserves a sensible thread order
</content>
</entry>
<entry>
<title>test: add known broken test for thread ordering from a loop</title>
<updated>2018-04-24T02:00:20Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2018-04-14T01:46:09Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=4e085b6d92909b8f6d4a4b18ccd97fac8b7df620'/>
<id>urn:sha1:4e085b6d92909b8f6d4a4b18ccd97fac8b7df620</id>
<content type='text'>
The previous loop handling code chooses the last message in the
message list, which turns out to be the last in date order.
See the comment in _notmuch_thread_create.
</content>
</entry>
<entry>
<title>lib: break reference loop by choosing arbitrary top level msg</title>
<updated>2018-04-20T14:23:31Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2018-04-14T01:08:05Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=9293d6da27494d7b607c945c6678bc890749b94f'/>
<id>urn:sha1:9293d6da27494d7b607c945c6678bc890749b94f</id>
<content type='text'>
Other parts of notmuch (e.g. notmuch show) expect each thread to
contain at least one top level message, and crash if this expectation
is not met.
</content>
</entry>
<entry>
<title>test: add known broken test for indexing an In-Reply-To loop.</title>
<updated>2018-04-20T14:23:31Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2018-03-20T21:22:35Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=ab55ca8e0a84b8e00e42860fa0025c1ae86b4478'/>
<id>urn:sha1:ab55ca8e0a84b8e00e42860fa0025c1ae86b4478</id>
<content type='text'>
This documents the bug discussed in

     id:87d10042pu.fsf@curie.anarc.at
</content>
</entry>
<entry>
<title>test: two new messages for the 'broken' corpus</title>
<updated>2018-04-20T14:23:31Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2018-03-20T21:22:34Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=044cbd920c6c68e741f1fb261c2710a0afb1ebad'/>
<id>urn:sha1:044cbd920c6c68e741f1fb261c2710a0afb1ebad</id>
<content type='text'>
These have an 'In-Reply-To' loop, which currently confuses "notmuch
new".
</content>
</entry>
<entry>
<title>cli/reply: make --decrypt take a keyword</title>
<updated>2017-12-29T20:45:55Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2017-12-19T16:40:55Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=af8255fb7159652a7d4e1fe4f1398302e1746cce'/>
<id>urn:sha1:af8255fb7159652a7d4e1fe4f1398302e1746cce</id>
<content type='text'>
This brings the --decrypt argument to "notmuch reply" into line with
the other --decrypt arguments (in "show", "new", "insert", and
"reindex").  This patch is really just about bringing consistency to
the user interface.

We also use the recommended form in the emacs MUA when replying, and
update test T350 to match.
</content>
</entry>
<entry>
<title>cli/show: make --decrypt take a keyword.</title>
<updated>2017-12-29T20:45:46Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2017-12-19T16:40:54Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=8ea4a99d74737929f58568505e41c94f65a14743'/>
<id>urn:sha1:8ea4a99d74737929f58568505e41c94f65a14743</id>
<content type='text'>
We also expand tab completion for it, update the emacs bindings, and
update T350, T357, and T450 to match.

Make use of the bool-to-keyword backward-compatibility feature.
</content>
</entry>
<entry>
<title>cli: some keyword options can be supplied with no argument</title>
<updated>2017-12-29T20:45:35Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2017-12-25T18:42:26Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=0ada2a05c94de72bc2c7c57a790e92b77af37a42'/>
<id>urn:sha1:0ada2a05c94de72bc2c7c57a790e92b77af37a42</id>
<content type='text'>
We might change some notmuch command line tools that used to be
booleans into keyword arguments.

In that case, there are some legacy tools that will expect to be able
to do "notmuch foo --bar" instead of "notmuch foo --bar=baz".

This patch makes it possible to support that older API, while
providing a warning and an encouragement to upgrade.
</content>
</entry>
<entry>
<title>python: add decrypt_policy argument to Database.index_file()</title>
<updated>2017-12-24T13:47:35Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2017-12-19T19:08:50Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=6aec7a76b9e70544a93b092c50d167c3e63548ee'/>
<id>urn:sha1:6aec7a76b9e70544a93b092c50d167c3e63548ee</id>
<content type='text'>
We adopt a pythonic idiom here with an optional argument, rather than
exposing the user to the C indexopts object directly.

This now includes a simple test to ensure that the decrypt_policy
argument works as expected.
</content>
</entry>
<entry>
<title>test: final named query test works regardless of Xapian FieldProcessor</title>
<updated>2017-12-21T13:35:20Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2017-12-19T16:27:39Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=b1de8e885d0cb150650f34acb074bcfdfd5c3840'/>
<id>urn:sha1:b1de8e885d0cb150650f34acb074bcfdfd5c3840</id>
<content type='text'>
This test passes with older versions of Xapian as well, because
neither query returns any results.

This should resolve the travis build failure at
https://travis-ci.org/notmuch/notmuch/builds/318571658

Signed-off-by: Daniel Kahn Gillmor &lt;dkg@fifthhorseman.net&gt;
</content>
</entry>
</feed>
