From: David Bremner <david@tethera.net>
To: Jani Nikula <jani@nikula.org>, Austin Clements <amdragon@MIT.EDU>,
notmuch@notmuchmail.org
Cc: tomi.ollila@iki.fi
Subject: Re: [PATCH v3 0/3] Clean up reply's encoding story
Date: Sat, 17 Aug 2013 17:21:55 +0200 [thread overview]
Message-ID: <87eh9s8hrg.fsf@maritornes.cs.unb.ca> (raw)
In-Reply-To: <8738q8jzh3.fsf@nikula.org>
Jani Nikula <jani@nikula.org> writes:
>
> 'make test' now gives me:
>
> FAIL Reply with RFC 2047-encoded headers
> --- reply.12.expected 2013-08-17 11:57:31.047782938 +0000
> +++ reply.12.output 2013-08-17 11:57:31.047782938 +0000
> @@ -1,5 +1,5 @@
> From: Notmuch Test Suite <test_suite@notmuchmail.org>
> -Subject: Re: =?iso-8859-1?b?4N/n?=
> +Subject: Re: =?iso-8859-1?B?4N/n?=
> To: =?UTF-8?b?4piD?= <snowman@example.com>
> In-Reply-To: <msg-012@notmuch-test-suite>
> References: <msg-012@notmuch-test-suite>
>
> I'm using libgmime 2.6.16-1 from Debian testing.
>
Oh hmm. now that I upgrade to 2.6.16-1 I see the same thing. It seems
like something changed in gmime. I think the RFC specifies that ?b is
equivalent to ?B as an encoding marker, so maybe we should normalize
before comparing?
d
prev parent reply other threads:[~2013-08-17 15:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-16 15:35 [PATCH v3 0/3] Clean up reply's encoding story Austin Clements
2013-08-16 15:35 ` [PATCH v3 1/3] reply: Test replying to messages with RFC 2047-encoded headers Austin Clements
2013-08-16 15:35 ` [PATCH v3 2/3] reply: Remove extraneous space from generated References Austin Clements
2013-08-16 15:35 ` [PATCH v3 3/3] reply: Use RFC 2822/MIME wholly for text format template Austin Clements
2013-08-16 15:45 ` [PATCH v3 0/3] Clean up reply's encoding story Jani Nikula
2013-08-16 20:27 ` Tomi Ollila
2013-08-17 7:07 ` David Bremner
2013-08-17 12:03 ` Jani Nikula
2013-08-17 15:21 ` David Bremner [this message]
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=87eh9s8hrg.fsf@maritornes.cs.unb.ca \
--to=david@tethera.net \
--cc=amdragon@MIT.EDU \
--cc=jani@nikula.org \
--cc=notmuch@notmuchmail.org \
--cc=tomi.ollila@iki.fi \
/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).