summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2017-07-25debian: add changelog entry for 0.25debian/0.25-10.25David Bremner
2017-07-25NEWS: set dateDavid Bremner
2017-07-25version: bump to 0.25David Bremner
2017-07-25NEWS: formatting fixupsDavid Bremner
These are from Tomi, split from the previous commit
2017-07-25NEWS for release 0.25: Emacs: support for stashing message timestampTomi Ollila
2017-07-18debian: changelog for 0.25~rc1-2debian/0.25_rc1-2David Bremner
2017-07-18debian: finalize changelog for 0.25~rc1-1debian/0.25_rc1-10.25_rc1David Bremner
2017-07-18version: bump to 0.25~rc1David Bremner
2017-07-18debian: allow emacs25 as a build dependDavid Bremner
It's a bit crazy to require emacs 24 installed just to build, when it isn't required to run.
2017-07-18emacs: convert remaining format-versions from 3 to 4David Bremner
This is needed for consistent beheviour between notmuch built against gmime-2.6 and gmime-3.0 w.r.t. error reporting.
2017-07-18fix the generated documentation outputDaniel Kahn Gillmor
2017-07-18Fix orthographyDaniel Kahn Gillmor
2017-07-18use modern debian/copyrightDaniel Kahn Gillmor
2017-07-18avoid false lintian warning about "iff"Daniel Kahn Gillmor
2017-07-18resolve lintian tag debhelper-but-no-misc-depends notmuch-emacsDaniel Kahn Gillmor
This is likely not strictly necessary given that notmuch-emacs is a transitional package. But having a simple consistency until we eventually remove the transitional notmuch-emacs package seems ok too, and fewer arbitrary lintian warnings will make real lintian warnings more visible.
2017-07-18fix Python capitalizationDaniel Kahn Gillmor
2017-07-18explicitly mark notmuch-emacs as transitionalDaniel Kahn Gillmor
2017-07-18Bump standards version to 4.0.0 (no changes needed)Daniel Kahn Gillmor
Some things that might be interesting (and are acceptable and supported under 4.0.0, though not required) are: * supporting DEB_BUILD_OPTIONS tag nodoc wihle tagging build-deps (we could put python-sphinx into <!nodoc>, for example) * splitting out Build-Depends-Arch from Build-Depends
2017-07-18Drop duplicate Section header for notmuch-vimDaniel Kahn Gillmor
Resolves lintian binary-control-field-duplicates-source
2017-07-18NEWS: drop redundant mention of dump fixDavid Bremner
This actually happened in 0.24.x.
2017-07-17Merge tag 'debian/0.25_rc0-2'David Bremner
merge 32 bit compilation fix
2017-07-17debian: changelog stanza for 0.25~rc0-2debian/0.25_rc0-2David Bremner
2017-07-17util: make g_mime_utils_header_decode_date_unix match prototypeDavid Bremner
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.
2017-07-16NEWS: Initial writeup for my contributions to 0.25David Bremner
2017-07-16Merge tag '0.25_rc0'David Bremner
notmuch 0.25~rc0 release
2017-07-16debian: note two closed bugs in changelogdebian/0.25_rc0-10.25_rc0David Bremner
2017-07-16debian: don't create obsolete bash completion dirDavid Bremner
2017-07-16debian: set distribution to experimental, finalize changelogDavid Bremner
2017-07-16debian: add more c++ gunk to symbols fileDavid Bremner
2017-07-16debian: bump changelog version, mention SONAME bumpDavid Bremner
2017-07-16NEWS: start entry for 0.25David Bremner
2017-07-16version: bump version to 0.25~rc0David Bremner
2017-07-15crypto: clean up unused definitions in gmime 3.0David Bremner
based on the same patch from dkg as the previous commit.
2017-07-15crypto: Avoid explicit handling of GMimeCryptoContext in gmime 3David Bremner
gmime 3.0 knows how to select the correct GMimeCryptoContext automatically, so a bunch of the code in notmuch can be dropped in that case. The #ifdef removal of the crypto stuff is better than #define aliasing in gmime-extra.h for this stuff. When built against gmime 3.0: * it reduces compiled code, and * it avoids initializing unused gpgme contexts (based on a patch from dkg)
2017-07-15cli/crypto: eliminated compiler warnings about unused argumentsDavid Bremner
These are due to (excessively?) fancy macro definitions in gmime-extra.h
2017-07-15cli/crypto: treat failure to create a crypto context as fatal.David Bremner
Silently ignoring signed/encrypted parts seems like the wrong idea, and it also complicates future gmime-3.0 compatibility changes.
2017-07-15emacs: change default for notmuch-crypto-process-mime to tDavid Bremner
There are some cases like remote usage where this might cause problems, but those users can easily customize the variable. The inconvenience seems to be outweighed by the security benefit for most users.
2017-07-15NEWS: a few formatting updates for 0.24 news items (wiki compatibility)Tomi Ollila
- removed 7 trailing dots -- to make those lines subsection headers - converted some (mime type) text to monospace - removed one extra space
2017-07-14clean up use of constants in g_mime_multipart_ wrappersDaniel Kahn Gillmor
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.
2017-07-14config: deprecate/drop crypto.gpg_path under gmime 2.6/3.0Daniel Kahn Gillmor
gmime 3.0 no longer offers a means to set the path for gpg. Users can set $PATH anyway if they want to pick a differently-installed gpg (e.g. /usr/local/bin/gpg), so this isn't much of a reduction in functionality. The one main difference is for people who have tried to use "gpg2" to make use of gpg 2.1, but that isn't usefully co-installable anyway.
2017-07-14Add additional munged reply-to testsDaniel Kahn Gillmor
The reply-to munging code might behave differently whether there's an exact match on the strings or not, or whether the string is a raw addr-spec instead of an name-addr. These tests cover those variations (i also had to tweak json output further below when this new test was added).
2017-07-14Ensure that "notmuch reply" succeeds during testing.Daniel Kahn Gillmor
In some (bad!) cases, "notmuch reply" might fail, or might even segfault. If this happens, it indicates a bug, and the test suite should notice it.
2017-07-14cli: wrap getting uidDavid Bremner
Apparently it moved from "name" to "key_id" in gmime-3.0
2017-07-14cli: make keyid from fingerprint in gmime 3.0David Bremner
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.
2017-07-14lib: paper over allocation differenceDavid Bremner
In gmime 3.0 this function is "transfer none", so no deallocation is needed (or permitted)
2017-07-14lib: add version of _n_m_f_get_combinded_header for gmime 3.0David Bremner
The iterator is gone, so we need a new loop structure.
2017-07-14lib: refactor _notmuch_messsage_file_get_combined_headerDavid Bremner
We need to rewrite the loop for gmime-3.0; move the loop body to its own function to avoid code duplication. Keep the common exit via "goto DONE" to make this pure code movement. It's important to note that the existing exit path only deallocates the iterator.
2017-07-14lib: wrap use of g_mime_utils_header_decode_dateDavid Bremner
This changes return type in gmime 3.0
2017-07-14cli: hide rename of GMimeCertificateTrustDavid Bremner
Both the enum and the values are renamed in GMime 3.0.
2017-07-14cli: generalize use of GMIME_SIGNATURE_{ERROR,STATUS} to gmime-3David Bremner
The ERROR enum is merged into to the STATUS enum, and the set of flags is different.
generated by cgit v1.2.3 (git 2.51.0) at 2026-06-23 16:36:02 +0000