From: Austin Clements <amdragon@MIT.EDU>
To: notmuch@notmuchmail.org
Subject: [PATCH 0/6] Clean up reply's encoding story
Date: Mon, 12 Aug 2013 14:40:33 -0400 [thread overview]
Message-ID: <1376332839-22825-1-git-send-email-amdragon@mit.edu> (raw)
Jeff Stedfast's email about gmime-filter-headers.c possibly being
unnecessary with GMime 2.6 (quoted in id:87bo56viyo.fsf@nikula.org)
sent me on a wild goose chase that led to this patch series. It
turned out that we *did* need gmime-filter-headers for what we were
doing in the reply text format, but what we were doing made no sense.
Patches 1 through 4 are simply the documentation and tests that I left
in my wake and are harmless to push. Patch 6 is my conclusion that
how we were handling header encoding in the text reply format made no
sense. Patch 5 is a step toward patch 6, but makes sense on its own
even if we decide against patch 6.
next reply other threads:[~2013-08-12 18:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-12 18:40 Austin Clements [this message]
2013-08-12 18:40 ` [PATCH 1/6] lib: Correct out-of-date doc comment Austin Clements
2013-08-12 18:40 ` [PATCH 2/6] lib: Document which strings are returned in UTF-8 Austin Clements
2013-08-12 18:40 ` [PATCH 3/6] reply: Document the reason for g_mime_filter_headers Austin Clements
2013-08-15 8:40 ` David Bremner
2013-08-12 18:40 ` [PATCH 4/6] reply: Test replying to messages with RFC 2047-encoded headers Austin Clements
2013-08-13 16:13 ` Austin Clements
2013-08-12 18:40 ` [PATCH 5/6] reply: Remove extraneous space from generated References Austin Clements
2013-08-12 18:40 ` [PATCH 6/6] reply: Use RFC 2822/MIME wholly for text format template Austin Clements
2013-08-12 20:01 ` Austin Clements
2013-08-14 17:04 ` [PATCH 0/6] Clean up reply's encoding story Tomi Ollila
2013-08-14 17:20 ` Austin Clements
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=1376332839-22825-1-git-send-email-amdragon@mit.edu \
--to=amdragon@mit.edu \
--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).