thread-based email index, search, and tagging https://git.notmuchmail.org/git/notmuch/atom?h=0.25.2 2017-11-06T00:06:23Z 2017-11-06T00:06:23Z David Bremner david@tethera.net 2017-11-06T00:06:23Z urn:sha1:83f266136369452b859393429b8530efac2e09fb 2017-11-05T23:59:30Z David Bremner david@tethera.net 2017-11-05T23:59:30Z urn:sha1:42871517c62c3b528d3b1ed792a7317877573345 2017-11-05T23:54:40Z David Bremner david@tethera.net 2017-11-05T23:54:40Z urn:sha1:58bf820b78f90c3db57fdd95a73fe76dc800733f 2017-11-05T19:41:13Z Jani Nikula jani@nikula.org 2017-10-16T15:40:44Z urn:sha1:cd3f5e1a934b9952ca718e0c5bc1471b3884020c Commit 1fdc08d0ffab ("cli/crypto: treat failure to create a crypto context as fatal.") started treating crypto context creation failures "as fatal", returning NULL from _mime_node_create(). Unfortunately, we do not have NULL checks for _mime_node_create() failures. The only caller, mime_node_child(), could check and return NULL (as it's documented to do on errors) but none of the several call sites have NULL checks either. And none of them really have a trivial but feasible and graceful way of recovery. So while the right thing to do would be to handle NULL returns properly all over the place, and we have other scenarios that do return NULL from above mentioned functions, the crypto context creation failure is something that does seem to show up regularly in some scenarios, revert back to the functionality before commit 1fdc08d0ffab as an interim fix. 2017-09-12T01:22:22Z David Bremner david@tethera.net 2017-09-12T01:22:22Z urn:sha1:949c27144e0b9294267511993a109c29d319a23d 2017-09-12T01:20:26Z David Bremner david@tethera.net 2017-09-12T01:20:26Z urn:sha1:aeeb966f95d9af626c72587b29be4b57ac216d53 2017-09-12T01:19:46Z David Bremner david@tethera.net 2017-09-12T01:19:46Z urn:sha1:0fa257cb740e6827d468aba1f3115f818f9da4c5 2017-09-12T01:08:01Z Jani Nikula jani@nikula.org 2017-09-11T20:09:49Z urn:sha1:9b0582383833c323b0b902dbe21ecf9cb0cce628 Switch to a local version of enriched-decode-display-prop if we encounter a text/enriched part. This is to mitigate https://bugs.gnu.org/28350. Normally it would be prudent to remove the override afterwards, but in this case just leave it in. Notes from db: This doesn't disable text/enriched, just one feature of it. 2017-08-17T00:38:26Z David Bremner david@tethera.net 2017-08-17T00:38:26Z urn:sha1:d7b5db32c3bf6b5e6c5f75d110355a9f5b5a59b8 2017-08-17T00:36:06Z Daniel Kahn Gillmor dkg@fifthhorseman.net 2017-07-20T06:28:52Z urn:sha1:34e5d4d31a32dd501cdd9981a64e291dbf6cefe8 see lintian's debian-news-entry-uses-asterisk for justification