<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/notmuch-client.h, branch 0.29</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=0.29</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=0.29'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2019-05-29T11:05:01Z</updated>
<entry>
<title>cli/show: emit payload subject instead of outside subject</title>
<updated>2019-05-29T11:05:01Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2019-05-26T22:15:58Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=1c7fbbcc99693c0433f7b06b569ce90c19ac5e1b'/>
<id>urn:sha1:1c7fbbcc99693c0433f7b06b569ce90c19ac5e1b</id>
<content type='text'>
Correctly fix the two outstanding tests so that the protected (hidden)
subject is properly reported.

Signed-off-by: Daniel Kahn Gillmor &lt;dkg@fifthhorseman.net&gt;
</content>
</entry>
<entry>
<title>cli: expose message-wide crypto status from mime-node</title>
<updated>2019-05-26T11:20:23Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2019-05-25T18:04:04Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=2c08beb2546156940e30526fc6759f4ee74b4fed'/>
<id>urn:sha1:2c08beb2546156940e30526fc6759f4ee74b4fed</id>
<content type='text'>
The mime node context (a per-message context) gains a cryptographic
status object, and the mime_node_t object itself can return a view on
that status to an interested party.

The status is not yet populated, and for now we can keep that view
read-only, so that it can only be populated/modified during MIME tree
traversal.
</content>
</entry>
<entry>
<title>gmime-cleanup: drop all arguments unused in GMime 3</title>
<updated>2019-05-03T09:56:38Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2019-05-02T13:19:41Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=b7ac4c05e118047442378f58eeb69d43bd1cbdb1'/>
<id>urn:sha1:b7ac4c05e118047442378f58eeb69d43bd1cbdb1</id>
<content type='text'>
This means dropping GMimeCryptoContext and notmuch_config arguments.

All the argument changes are to internal functions, so this is not an
API or ABI break.

We also get to drop the #define for g_mime_3_unused.

signed-off-by: Daniel Kahn Gillmor &lt;dkg@fifthhorseman.net&gt;
</content>
</entry>
<entry>
<title>gmime-cleanup: remove obsolete gpg_path configuration option and crypto contexts</title>
<updated>2019-05-03T09:55:04Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2019-05-02T13:19:36Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=096d45a878ba9606f1677f66d346b14c3c274fa5'/>
<id>urn:sha1:096d45a878ba9606f1677f66d346b14c3c274fa5</id>
<content type='text'>
Note that we do keep ignoring the gpg_path configuration option,
though, to avoid breakage of existing installations.  It is ignored
like any other unknown configuration option, but we at least document
that it is ignored so that people who find it in their legacy configs
can know that it's safe to drop.

signed-off-by: Daniel Kahn Gillmor &lt;dkg@fifthhorseman.net&gt;
</content>
</entry>
<entry>
<title>cli: add print_status_message()</title>
<updated>2018-05-26T14:32:14Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2018-05-11T06:57:55Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=f32e52448b8665dbf335fd97a21b49108e05a6c0'/>
<id>urn:sha1:f32e52448b8665dbf335fd97a21b49108e05a6c0</id>
<content type='text'>
This function is a parallel to print_status_query() or
print_status_database().  Thanks to David Bremner for the suggestion!
</content>
</entry>
<entry>
<title>crypto: new decryption policy "auto"</title>
<updated>2017-12-08T12:07:53Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2017-12-08T06:23:53Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=e4890b5bf9e2260b36bcc36ddb77d8e97e2abe7d'/>
<id>urn:sha1:e4890b5bf9e2260b36bcc36ddb77d8e97e2abe7d</id>
<content type='text'>
This new automatic decryption policy should make it possible to
decrypt messages that we have stashed session keys for, without
incurring a call to the user's asymmetric keys.
</content>
</entry>
<entry>
<title>lib: convert notmuch decryption policy to an enum</title>
<updated>2017-12-08T12:07:02Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2017-12-08T06:23:52Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=798aa789b5d117cf11697bc97dd982bd5a2c2ac8'/>
<id>urn:sha1:798aa789b5d117cf11697bc97dd982bd5a2c2ac8</id>
<content type='text'>
Future patches in this series will introduce new policies; this merely
readies the way for them.

We also convert --try-decrypt to a keyword argument instead of a boolean.
</content>
</entry>
<entry>
<title>indexopts: change _try_decrypt to _decrypt_policy</title>
<updated>2017-12-08T12:06:03Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2017-12-08T06:23:51Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=b62045a18680720b407173140d79b459e45e6039'/>
<id>urn:sha1:b62045a18680720b407173140d79b459e45e6039</id>
<content type='text'>
This terminology makes it clearer what's going on at the API layer,
and paves the way for future changesets that offer more nuanced
decryption policy.
</content>
</entry>
<entry>
<title>cli: set up shared command-line arguments for indexing</title>
<updated>2017-10-21T22:58:11Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2017-10-21T02:25:44Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=5bdb8549f619bbcd9fcd6161749dabbb1710dab9'/>
<id>urn:sha1:5bdb8549f619bbcd9fcd6161749dabbb1710dab9</id>
<content type='text'>
We have an indexopts structure for manipulating indexing in different
ways, but we also have three command-line invocations that can trigger
indexing: new, insert, and reindex.

This changeset prepares a common parser that these subcommands can
share.

Note: if the deprecated crypto.gpg_path configuration option is set to
anything other than "gpg", we ignore it (and print a warning on
stderr, if built against gmime &lt; 3.0).

At the moment, it's just --try-decrypt, but others will likely follow.
</content>
</entry>
<entry>
<title>crypto: move into libnotmuch_util</title>
<updated>2017-10-20T10:58:10Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2017-10-17T19:09:55Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=197d67959bf459fc0f1f63a202d162a569535bf3'/>
<id>urn:sha1:197d67959bf459fc0f1f63a202d162a569535bf3</id>
<content type='text'>
This prepares us for using the crypto object in both libnotmuch and
the client.
</content>
</entry>
</feed>
