notmuch, branch debian/0.39-1 thread-based email index, search, and tagging https://git.notmuchmail.org/git/notmuch/atom?h=debian%2F0.39-1 2025-03-15T22:45:14Z debian: drop patches 2025-03-15T22:45:14Z David Bremner david@tethera.net 2025-03-15T22:45:14Z urn:sha1:14f7a8929abedc465e30e8ec77c1bea72db35d9d Those changes are now directly in git. Merge branch 'debian/unstable' into release 2025-03-15T22:44:37Z David Bremner david@tethera.net 2025-03-15T22:44:37Z urn:sha1:65932712721569c0853c7ad53b310c5420cc6788 merge bugfix uploads from other branch NEWS: set release date 2025-03-15T22:04:35Z David Bremner david@tethera.net 2025-03-15T22:04:35Z urn:sha1:a5214eabb63ba78b84f4563942de1aa8763f0914 debian: changelog stanza for 0.39-1 2025-03-15T17:21:28Z David Bremner david@tethera.net 2025-03-15T10:04:26Z urn:sha1:8fdb713d2facc25bfb075f9152e9ff1d7ae39b48 version: bump to 0.39 2025-03-15T17:21:28Z David Bremner david@tethera.net 2025-03-15T09:55:51Z urn:sha1:dea40c9dd68c14756c5a4ab108fe0597f2e6da2e Identical to 0.39~rc3, except for release related documentation (e.g. NEWS). NEWS: news for 0.39 2025-03-15T17:21:12Z David Bremner david@tethera.net 2025-03-15T09:46:42Z urn:sha1:e916fbd846f8fd8c2597167bb09ca2a9fa2244e5 This is based on my reading of git shortlog. Some more development specific changes have been omitted. debian: changelog for 0.39~rc3-1 2025-03-14T22:07:38Z David Bremner david@tethera.net 2025-03-14T22:07:38Z urn:sha1:fd32351ce02353ddbb9b04479505240d51b52b84 version: bump to 0.39~rc3 2025-03-14T22:06:12Z David Bremner david@tethera.net 2025-03-14T22:06:12Z urn:sha1:9762b4cc6eeef4e8b01e0d4b0f62d2482e9b5f87 Set 'untrusted-content' to t in all modes 2025-03-14T11:51:02Z Stefan Kangas stefankangas@gmail.com 2025-03-12T09:36:21Z urn:sha1:df4c1b5be769effb2ef7bc85c8bb8e09fb8f43fc Instead of trying to guess in which modes this is safe not to set in, let's just set it in all of them. Background (added by db): untrusted-content was added in Emacs 29.3 and is currently set by Gnus and used by org-mode to prevent certain unsafe operations. I think the intent is to use it for blocking more unsafe operations in the future. bindings/python-cffi: fix docstring for message.header() 2025-03-14T00:18:15Z Michael J Gruber git@grubix.eu 2025-03-04T12:39:43Z urn:sha1:5802f5d6269172222a6fccf5908eae833014917b The cffi bindings raise a LookupError in case a header is not present. Adjust the docstring to say so. The legacy bindings behaved differently, and this is one of the things to be aware of when migrating to the cffi bindings.