<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch, branch 0.29_rc1</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=0.29_rc1</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=0.29_rc1'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2019-06-03T11:10:19Z</updated>
<entry>
<title>debian: changelog for 0.29~rc1-1</title>
<updated>2019-06-03T11:10:19Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2019-06-03T11:10:19Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=5228e06e09fbc61e0db9e68216d97ea7adb34f32'/>
<id>urn:sha1:5228e06e09fbc61e0db9e68216d97ea7adb34f32</id>
<content type='text'>
</content>
</entry>
<entry>
<title>version: bump to 0.29~rc1</title>
<updated>2019-06-03T11:08:00Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2019-06-03T11:08:00Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=fd97ef8a645605929db26d56851748e03a1fa13f'/>
<id>urn:sha1:fd97ef8a645605929db26d56851748e03a1fa13f</id>
<content type='text'>
</content>
</entry>
<entry>
<title>doc: use separate doctrees for distinct builders</title>
<updated>2019-06-03T10:35:30Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2019-06-01T02:24:52Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=6edc073e4496b71d24e339f4d0cca41c2e4ac3e1'/>
<id>urn:sha1:6edc073e4496b71d24e339f4d0cca41c2e4ac3e1</id>
<content type='text'>
It seems our previous attempt with order-only targets was not
sufficient to avoid problems with sphinx-builds doctree cache [0].
Looking around at other people's approaches [1], using separate
doctrees was suggested. I guess there might be a slight loss of
efficiency, but it seems more robust.

[0]: build failures were first noticed in Debian experimental, but I was able to duplicate it in
     my usual build environment about 1 in 8 builds.

[1]: in particular
     https://salsa.debian.org/mpd-team/mpc/commit/9e3fc1657d043d75755993846c93f7700b97f907
</content>
</entry>
<entry>
<title>debian: changelog for 0.29~rc0-1</title>
<updated>2019-05-31T11:24:55Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2019-05-31T11:16:34Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=80cfc48af550f66837ad3822a2db18b916487eea'/>
<id>urn:sha1:80cfc48af550f66837ad3822a2db18b916487eea</id>
<content type='text'>
</content>
</entry>
<entry>
<title>version: bump to 0.29~rc0</title>
<updated>2019-05-31T11:11:12Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2019-05-31T11:11:12Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=a425a010c985dc7c80a59a302d35e7723fc63f30'/>
<id>urn:sha1:a425a010c985dc7c80a59a302d35e7723fc63f30</id>
<content type='text'>
</content>
</entry>
<entry>
<title>mime-node: be clearer about decryption</title>
<updated>2019-05-31T10:55:46Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2019-05-31T01:18:53Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=d439e4b5d1715b96baba5e0fa5b1b81e9746a94c'/>
<id>urn:sha1:d439e4b5d1715b96baba5e0fa5b1b81e9746a94c</id>
<content type='text'>
Part 0 of a multipart/encrypted object is
GMIME_MULTIPART_ENCRYPTED_VERSION; part 1 is
GMIME_MULTIPART_ENCRYPTED_CONTENT.  Using the name for what we want
describes our intent more clearly than using a magic number in the
code.

Signed-off-by: Daniel Kahn Gillmor &lt;dkg@fifthhorseman.net&gt;
</content>
</entry>
<entry>
<title>test: update test description.</title>
<updated>2019-05-29T11:40:02Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2019-05-29T11:40:02Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=2c1e5c186ee36fb215d3f312f9801884f4720d8f'/>
<id>urn:sha1:2c1e5c186ee36fb215d3f312f9801884f4720d8f</id>
<content type='text'>
I missed this fix in dkg's revisions.
</content>
</entry>
<entry>
<title>cli/reply: pull proposed subject line from the message, not the index</title>
<updated>2019-05-29T11:17:33Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2019-05-26T22:16:10Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=1c704dd22d81b2d6307125d47cc895127f8e34c9'/>
<id>urn:sha1:1c704dd22d81b2d6307125d47cc895127f8e34c9</id>
<content type='text'>
Protected subject lines were being emitted in reply when the cleartext
of documents was indexed.  create_reply_message() was pulling the
subject line from the index, rather than pulling it from the
GMimeMessage object that it already has on hand.

This one-line fix to notmuch-reply.c solves that problem, and doesn't
cause any additional tests to fail.

Signed-off-by: Daniel Kahn Gillmor &lt;dkg@fifthhorseman.net&gt;
</content>
</entry>
<entry>
<title>test: reply (in cli and emacs) should protect indexed sensitive headers</title>
<updated>2019-05-29T11:17:20Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2019-05-26T22:16:09Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=06dedd0a8365ee4b71f730651e00b1098369f9b9'/>
<id>urn:sha1:06dedd0a8365ee4b71f730651e00b1098369f9b9</id>
<content type='text'>
These tests are currently broken!  When a protected subject is indexed
in the clear, it leaks in the reply headers :(

For emacs, we set up separate tests for when the protected header is
indexed in the clear and when it is unindexed.  neither case should
leak, but the former wasn't tested yet.

We will fix the two broken tests in a subsequent patch.

Signed-off-by: Daniel Kahn Gillmor &lt;dkg@fifthhorseman.net&gt;
</content>
</entry>
<entry>
<title>test: emacs/show: ensure that protected headers appear as expected</title>
<updated>2019-05-29T11:17:12Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2019-05-26T22:16:08Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=cd8006886b1c80ff556a96f1e84e3d3914067a54'/>
<id>urn:sha1:cd8006886b1c80ff556a96f1e84e3d3914067a54</id>
<content type='text'>
This tests notmuch-show; headers appear appropriately based on the
setting of notmuch-crypto-process-mime.

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