notmuch/util, branch 0.25.1 thread-based email index, search, and tagging https://git.notmuchmail.org/git/notmuch/atom?h=0.25.1 2017-07-17T11:47:18Z util: make g_mime_utils_header_decode_date_unix match prototype 2017-07-17T11:47:18Z David Bremner david@tethera.net 2017-07-17T11:47:18Z urn:sha1:d2c3a0a3a849fdc8ce2f908b2c0d6e7197f07ae1 The problem shows up on 32 bit architectures where sizeof(time_t) != sizeof(gint64). Upcasting the 32 bit time_t to a 64 bit integer should hopefully be safe. cli/crypto: eliminated compiler warnings about unused arguments 2017-07-16T00:42:49Z David Bremner david@tethera.net 2017-07-15T23:01:44Z urn:sha1:606e320e472b486359cf7a44c488b29e717a3ac8 These are due to (excessively?) fancy macro definitions in gmime-extra.h clean up use of constants in g_mime_multipart_ wrappers 2017-07-15T00:23:52Z Daniel Kahn Gillmor dkg@fifthhorseman.net 2017-07-14T13:12:01Z urn:sha1:f76a245009b8db6065d83a0e86df697003f41b77 When compiling as C code (instead of C++) against gmime 3.0, gcc gives errors like the following: error: invalid conversion from ‘int’ to ‘GMimeDecryptFlags’ [-fpermissive] so use explicit *_NONE values instead. cli: wrap getting uid 2017-07-15T00:23:52Z David Bremner david@tethera.net 2017-06-03T00:19:04Z urn:sha1:cd853915ec0ad3e3ee6ec90a7d856e95d001abe9 Apparently it moved from "name" to "key_id" in gmime-3.0 cli: make keyid from fingerprint in gmime 3.0 2017-07-15T00:23:52Z David Bremner david@tethera.net 2017-06-02T23:57:01Z urn:sha1:2b3224a6c4be6b6c038a9956448187e0a402687b The "key_id" field seems to used for userid in gmime-3.0, while the keyid is dropped in the fingerprint field if the full fingerprint is not available. lib: paper over allocation difference 2017-07-15T00:23:52Z David Bremner david@tethera.net 2017-05-20T12:05:22Z urn:sha1:4ce7591610444a1c5ef6f56b57af8e180437fa62 In gmime 3.0 this function is "transfer none", so no deallocation is needed (or permitted) lib: wrap use of g_mime_utils_header_decode_date 2017-07-15T00:23:52Z David Bremner david@tethera.net 2017-05-17T01:59:54Z urn:sha1:c040464a7c8f339d15f691113b8f5fd901229bcb This changes return type in gmime 3.0 cli: hide rename of GMimeCertificateTrust 2017-07-15T00:23:52Z David Bremner david@tethera.net 2017-05-14T17:51:38Z urn:sha1:fd6e4a99535cb5142381803bc4ea4f4f79d8d459 Both the enum and the values are renamed in GMime 3.0. cli: generalize use of GMIME_SIGNATURE_{ERROR,STATUS} to gmime-3 2017-07-15T00:23:52Z David Bremner david@tethera.net 2017-05-14T17:49:31Z urn:sha1:c7b9bdb81e49321170dc6f0a522301f28e791521 The ERROR enum is merged into to the STATUS enum, and the set of flags is different. util: fake gmime-2.6 compatible API for gmime-3.0 2017-07-14T20:58:09Z David Bremner david@tethera.net 2017-05-06T11:54:32Z urn:sha1:f4a989484fb678ad2c1adf84b842451208a08ad5 Several functions have added arguments which accept NULL and provide hopefully sensible defaults. Use macros to minimize source changes.