From: David Bremner <david@tethera.net>
To: notmuch@notmuchmail.org
Subject: Re: [PATCH] test: canonicalize content-type in "Sending a message via (fake) SMTP"
Date: Fri, 31 Aug 2012 08:48:52 -0300 [thread overview]
Message-ID: <87txvjcme3.fsf@zancas.localnet> (raw)
In-Reply-To: <1346369074-8366-1-git-send-email-david@tethera.net>
david@tethera.net writes:
> From: David Bremner <bremner@debian.org>
>
> The version of message.el in emacs24 omits the charset=us-ascii,
> causing the current version of this test to fail. With this patch, we
> accept either option. According to RFC 2046, they are semantically
> equivalent.
Pushed the second one.
d
prev parent reply other threads:[~2012-08-31 11:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-30 1:12 [PATCH] test: canonicalize content-type in "Sending a message via (fake) SMTP" david
2012-08-30 1:36 ` Austin Clements
2012-08-30 23:24 ` david
2012-08-31 3:49 ` Austin Clements
2012-08-31 7:14 ` Tomi Ollila
2012-08-31 11:48 ` 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=87txvjcme3.fsf@zancas.localnet \
--to=david@tethera.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).