From: David Bremner <david@tethera.net>
To: notmuch@notmuchmail.org, notmuch@freelists.org
Subject: gmime 3.0 related preliminaries
Date: Sun, 21 May 2017 09:48:16 -0300 [thread overview]
Message-ID: <20170521124821.23924-1-david@tethera.net> (raw)
I've been working away on porting to gmime 3.0 [1]; currently more
than 50 tests fail, at least some of which due to [2].
I've also found a few bugs in notmuch:
We currently use GmimeFileStream to output to stdout, but this assumes
the underlying file descriptor is seekable; the seek errors are masked
in gmime 2.6 but not in gmime 3.0
[PATCH 1/5] util: convenience function to create gmime stream for
[PATCH 2/5] cli/reply: direct all output for text format to gmime
[PATCH 3/5] cli/show: use single stream for printf / gmime object
There is also memory leak in notmuch reply; because notmuch-reply
doesn't run for a long time, the practical impact is low. The first
patch is just so we have some way of verifying the fix. It seems a bit
heavy to start using valgrind in the main test suite.
[1]: http://pivot.cs.unb.ca/git?p=notmuch.git;a=shortlog;h=refs/heads/gmime-3.0
[2]: https://bugzilla.gnome.org/show_bug.cgi?id=782915
next reply other threads:[~2017-05-21 12:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-21 12:48 David Bremner [this message]
2017-05-21 12:48 ` [PATCH 1/5] util: convenience function to create gmime stream for stdout David Bremner
2017-05-21 13:28 ` David Bremner
2017-05-21 15:34 ` David Bremner
2017-05-21 12:48 ` [PATCH 2/5] cli/reply: direct all output for text format to gmime stream David Bremner
2017-05-21 12:48 ` [PATCH 3/5] cli/show: use single stream for printf / gmime object output David Bremner
2017-05-21 12:48 ` [PATCH 4/5] perf-test: add memory test for reply David Bremner
2017-05-21 12:48 ` [PATCH 5/5] cli/reply: fix memory leak David Bremner
2017-05-21 13:17 ` David Bremner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170521124821.23924-1-david@tethera.net \
--to=david@tethera.net \
--cc=notmuch@freelists.org \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).