From: David Bremner <david@tethera.net>
To: Thomas Schwinge <thomas@schwinge.name>, notmuch@notmuchmail.org
Subject: Re: [PATCH] restore: Be more liberal in which data to accept.
Date: Tue, 15 Nov 2011 09:52:43 -0400 [thread overview]
Message-ID: <87fwhpbihg.fsf@zancas.localnet> (raw)
In-Reply-To: <1319884807-7206-1-git-send-email-thomas@schwinge.name>
On Sat, 29 Oct 2011 12:40:07 +0200, Thomas Schwinge <thomas@schwinge.name> wrote:
> From: Thomas Schwinge <thomas@schwinge.name>
>
> There are ``Message-ID''s out in the wild that contain spaces.
>
> ---
> Carl, the main question for you is: does this break sup-import
> operability?
Any other sup users care to comment?
next prev parent reply other threads:[~2011-11-15 13:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-29 10:40 [PATCH] restore: Be more liberal in which data to accept Thomas Schwinge
2011-11-15 13:52 ` David Bremner [this message]
2012-01-07 13:37 ` David Bremner
2012-01-07 18:20 ` Jameson Graef Rollins
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=87fwhpbihg.fsf@zancas.localnet \
--to=david@tethera.net \
--cc=notmuch@notmuchmail.org \
--cc=thomas@schwinge.name \
/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).