<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/notmuch-client.h, branch debian/stretch</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=debian%2Fstretch</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=debian%2Fstretch'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2017-04-02T00:08:32Z</updated>
<entry>
<title>cli/dump: bump dump format version to 3</title>
<updated>2017-04-02T00:08:32Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2017-03-31T10:55:17Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=87f1d68440c3126a585427443339ff4c8e3067ef'/>
<id>urn:sha1:87f1d68440c3126a585427443339ff4c8e3067ef</id>
<content type='text'>
No changes to the format of the body, but the header format was
fixed, and version 2 headers probably shouldn't be relied on.
</content>
</entry>
<entry>
<title>cli/insert: return EX_TEMPFAIL for some errors</title>
<updated>2016-12-07T11:00:40Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2016-11-28T03:01:42Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=d74c5345704136611f993ca38e0d035b1da798b6'/>
<id>urn:sha1:d74c5345704136611f993ca38e0d035b1da798b6</id>
<content type='text'>
Attempt to distinguish between errors indicating misconfiguration or
programmer error, which we consider "permanent", in the sense that
automatic retries are unlikely to be useful, and those indicating
transient error conditions. We consider XAPIAN_EXCEPTION transient
because it covers the important special case of locking failure.
</content>
</entry>
<entry>
<title>cli: consider files vanishing during notmuch new non-fatal</title>
<updated>2016-11-26T01:09:32Z</updated>
<author>
<name>Jani Nikula</name>
<email>jani@nikula.org</email>
</author>
<published>2016-11-21T20:14:33Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=f5185881f7b01f67b5b64218804749b733f08d44'/>
<id>urn:sha1:f5185881f7b01f67b5b64218804749b733f08d44</id>
<content type='text'>
If some software other than notmuch new renames or removes files
during the notmuch new scan (specifically after scandir but before
indexing the file), keep going instead of bailing out. Failing to
index the file is just a race condition between notmuch and the other
software; the rename could happen after the notmuch new scan
anyway. It's not fatal, and we'll catch the renamed files on the next
scan.

Add a new exit code for when files vanished, so the caller has a
chance to detect the race and re-run notmuch new to recover.

Reported by Paul Wise &lt;pabs@debian.org&gt; at
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843127
</content>
</entry>
<entry>
<title>CLI: add properties to dump output</title>
<updated>2016-09-21T21:14:25Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2016-06-13T01:05:54Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=b7345d277ec5f562000c0e740e6515c2a84f9c76'/>
<id>urn:sha1:b7345d277ec5f562000c0e740e6515c2a84f9c76</id>
<content type='text'>
Part of providing extensibility via properties is to make sure that user
data is not lost. Thus we need to be able to dump and restore
properties.
</content>
</entry>
<entry>
<title>Use https instead of http where possible</title>
<updated>2016-06-05T11:32:17Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2016-06-02T16:26:14Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=6a833a6e83865f6999707cc30768d07e1351c2cb'/>
<id>urn:sha1:6a833a6e83865f6999707cc30768d07e1351c2cb</id>
<content type='text'>
Many of the external links found in the notmuch source can be resolved
using https instead of http.  This changeset addresses as many as i
could find, without touching the e-mail corpus or expected outputs
found in tests.
</content>
</entry>
<entry>
<title>CLI: add optional config data to dump output.</title>
<updated>2016-05-25T10:07:56Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2016-03-22T10:54:50Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=e042a25a3fd8706b6e1ee7bdf527bb17ecb74c6a'/>
<id>urn:sha1:e042a25a3fd8706b6e1ee7bdf527bb17ecb74c6a</id>
<content type='text'>
Note that it changes the default dump output format, but doesn't break
existing notmuch-restore. It might break user scripts though.
</content>
</entry>
<entry>
<title>CLI: add print_status_database</title>
<updated>2016-03-30T01:59:35Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2016-01-10T01:34:21Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=ccf0db161590e2aac7db0e049547c347ab4db528'/>
<id>urn:sha1:ccf0db161590e2aac7db0e049547c347ab4db528</id>
<content type='text'>
This could probably be used at quite a few places in the existing code,
but in the immediate future I plan to use in some new code in
notmuch-dump
</content>
</entry>
<entry>
<title>cli: crypto: S/MIME verification support</title>
<updated>2016-01-29T21:45:46Z</updated>
<author>
<name>Jani Nikula</name>
<email>jani@nikula.org</email>
</author>
<published>2015-08-16T17:41:14Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=2355f1522ae77a1012ca3ef08d97098a5951d142'/>
<id>urn:sha1:2355f1522ae77a1012ca3ef08d97098a5951d142</id>
<content type='text'>
notmuch-show --verify will now also process S/MIME multiparts if
encountered. Requires gmime-2.6 and gpgsm.

Based on work by Jameson Graef Rollins &lt;jrollins@finestructure.net&gt;.
</content>
</entry>
<entry>
<title>cli: change the data structure for notmuch address deduplication</title>
<updated>2015-09-26T10:37:54Z</updated>
<author>
<name>Jani Nikula</name>
<email>jani@nikula.org</email>
</author>
<published>2015-09-25T16:48:20Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=b8f4e7da3d61733fb47111b162ccabb967a3661e'/>
<id>urn:sha1:b8f4e7da3d61733fb47111b162ccabb967a3661e</id>
<content type='text'>
Currently we key the address hash table with the case sensitive "name
&lt;address&gt;". Switch to case insensitive keying with just address, and
store the case sensitive name and address in linked lists. This will
be helpful in adding support for different deduplication schemes in
the future.

There will be a slight performance penalty for the current full case
sensitive name + address deduplication, but this is simpler as a whole
when other deduplication schemes are added, and I expect the schemes
to be added to become more popular than the current default.

Aparet from the possible performance penalty, the only user visible
change should be the change in the output ordering for
--output=count. The order is not guaranteed (and is based on hash
table traversal) currently anyway, so this should be of no
consequence.
</content>
</entry>
<entry>
<title>cli: add utility routine to print error status.</title>
<updated>2015-09-20T11:04:31Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2015-09-06T13:15:45Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=39c54df26dad01e3ec294f7c4a613d9ee71faf3e'/>
<id>urn:sha1:39c54df26dad01e3ec294f7c4a613d9ee71faf3e</id>
<content type='text'>
No attention to formatting here, initially just focus on getting the
relevant strings out of the library.
</content>
</entry>
</feed>
