From: Jani Nikula <jani@nikula.org>
To: notmuch@notmuchmail.org
Cc: Daniel Kahn Gillmor <dkg@fifthhorseman.net>, jani@nikula.org
Subject: [PATCH v2 00/14] reply refactor, fixes
Date: Sat, 13 Aug 2016 14:37:24 +0300 [thread overview]
Message-ID: <cover.1471088022.git.jani@nikula.org> (raw)
Hi all, this lengthy series fixes replies to messages with multiple Cc:
headers. Daniel reported the problem in
id:87d1ngv95p.fsf@alice.fifthhorseman.net.
Lots of refactoring is required to switch to using more GMime functions
in the reply code.
This is v2 of the series in id:cover.1466284726.git.jani@nikula.org.
BR,
Jani.
Jani Nikula (14):
test: add known broken test for reply to message with multiple Cc
headers
cli/reply: push notmuch reply format abstraction lower in the stack
cli/reply: reuse show_reply_headers() in headers-only format
cli/reply: unify reply format functions
cli/reply: reorganize create_reply_message()
cli/reply: make references header creation easier to follow
cli/reply: reuse create_reply_message() also for headers-only format
cli/reply: reduce the reply format abstractions
cli/reply: use dedicated functions for reply to mapping
cli/reply: check for NULL list first in scan_address_list()
cli/reply: return internet address list from get header funcs
cli/reply: pass internet address list to munge detect
cli/reply: pass gmime message to munge detection
cli/reply: only pass gmime message to add recipients to reply message
notmuch-reply.c | 435 +++++++++++++++++++++--------------------------------
test/T220-reply.sh | 24 +++
2 files changed, 192 insertions(+), 267 deletions(-)
--
2.1.4
next reply other threads:[~2016-08-13 11:39 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-13 11:37 Jani Nikula [this message]
2016-08-13 11:37 ` [PATCH v2 01/14] test: add known broken test for reply to message with multiple Cc headers Jani Nikula
2016-09-10 0:43 ` David Bremner
2016-09-10 22:17 ` David Bremner
2016-09-11 11:49 ` Jani Nikula
2016-08-13 11:37 ` [PATCH v2 02/14] cli/reply: push notmuch reply format abstraction lower in the stack Jani Nikula
2016-09-10 0:53 ` David Bremner
2016-09-10 6:20 ` Jani Nikula
2016-08-13 11:37 ` [PATCH v2 03/14] cli/reply: reuse show_reply_headers() in headers-only format Jani Nikula
2016-08-13 11:37 ` [PATCH v2 04/14] cli/reply: unify reply format functions Jani Nikula
2016-09-10 1:38 ` David Bremner
2016-09-10 6:26 ` Jani Nikula
2016-08-13 11:37 ` [PATCH v2 05/14] cli/reply: reorganize create_reply_message() Jani Nikula
2016-09-10 16:21 ` David Bremner
2016-08-13 11:37 ` [PATCH v2 06/14] cli/reply: make references header creation easier to follow Jani Nikula
2016-09-10 16:23 ` David Bremner
2016-08-13 11:37 ` [PATCH v2 07/14] cli/reply: reuse create_reply_message() also for headers-only format Jani Nikula
2016-08-13 11:37 ` [PATCH v2 08/14] cli/reply: reduce the reply format abstractions Jani Nikula
2016-09-10 16:33 ` David Bremner
2016-08-13 11:37 ` [PATCH v2 09/14] cli/reply: use dedicated functions for reply to mapping Jani Nikula
2016-08-13 11:37 ` [PATCH v2 10/14] cli/reply: check for NULL list first in scan_address_list() Jani Nikula
2016-08-13 11:37 ` [PATCH v2 11/14] cli/reply: return internet address list from get header funcs Jani Nikula
2016-09-10 22:46 ` David Bremner
2016-08-13 11:37 ` [PATCH v2 12/14] cli/reply: pass internet address list to munge detect Jani Nikula
2016-09-10 22:51 ` David Bremner
2016-08-13 11:37 ` [PATCH v2 13/14] cli/reply: pass gmime message to munge detection Jani Nikula
2016-09-10 22:58 ` David Bremner
2016-08-13 11:37 ` [PATCH v2 14/14] cli/reply: only pass gmime message to add recipients to reply message Jani Nikula
2016-09-10 23:00 ` 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=cover.1471088022.git.jani@nikula.org \
--to=jani@nikula.org \
--cc=dkg@fifthhorseman.net \
--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).