unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: David Bremner <david@tethera.net>
To: Jeffrey Stedfast <jestedfa@microsoft.com>,
	"notmuch@notmuchmail.org" <notmuch@notmuchmail.org>
Cc: notmuch@freelists.org
Subject: RE: Upcoming GMime 3.0 changes
Date: Tue, 09 May 2017 10:37:30 -0300	[thread overview]
Message-ID: <87k25q178l.fsf@tesseract.cs.unb.ca> (raw)
In-Reply-To: <CY4PR21MB0629BF6AAAEFA9D058B7C247CF240@CY4PR21MB0629.namprd21.prod.outlook.com>

Jeffrey Stedfast <jestedfa@microsoft.com> writes:

>> -----Original Message-----
>> From: David Bremner [mailto:david@tethera.net]
>> Sent: Tuesday, March 14, 2017 9:18 AM
>> To: Jeffrey Stedfast <jestedfa@microsoft.com>; notmuch@notmuchmail.org
>> Subject: Re: Upcoming GMime 3.0 changes
>> 
>> Jeffrey Stedfast <jestedfa@microsoft.com> writes:
>> 
>> > Hello notmuch devs,
>> >
>> > I'm sending this email to inform you guys of some upcoming GMime 3.0
>> features and other changes that I've implemented.
>> >

Just for the record, I have some patches in progress for porting to
gmime-3.0. The main issue is the multiplicity of memory management
models involved. I think the gmime 3.0 approach of using more stock glib
memory management makes sense, but it will require a bit of work to make
code that can compile against gmime-2.6 and gmime-3.0. I don't see us
being able to drop support for gmime-2.6 for a few years, unfortunately.

d

  reply	other threads:[~2017-05-09 13:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-13 22:43 Upcoming GMime 3.0 changes Jeffrey Stedfast
2017-03-14 13:17 ` David Bremner
2017-03-14 18:03   ` Jeffrey Stedfast
2017-05-09 13:37     ` David Bremner [this message]
2017-05-09 17:02       ` Daniel Kahn Gillmor
2017-05-09 18:49         ` David Bremner
2017-05-09 20:02           ` Tomi Ollila

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=87k25q178l.fsf@tesseract.cs.unb.ca \
    --to=david@tethera.net \
    --cc=jestedfa@microsoft.com \
    --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).