From: Wolfgang Jenkner <wjen...@inode.at>
To: Leah Neukirchen <le...@vuxu.org>
Cc: mbl...@googlegroups.com
Subject: Re: [PATCH] Fix non-POSIX sed usage
Date: Wed, 12 Jul 2017 20:22:53 +0200 [thread overview]
Message-ID: <ERNX3CSOLA.2VZMT4QLSH7WK@inode.at> (raw)
In-Reply-To: <878tjyrcgq.fsf@gmail.com>
Leah Neukirchen <le...@vuxu.org> wrote:
> > Subject: [PATCH] Fix non-POSIX sed usage
>
> Thanks, applied!
Thank you.
There's still a point about the 'References' header which puzzles me:
mrep puts two spaces between 'References:' and the first message-id (at
line 148 and line 17 in mcom). So, if the message-id is sufficiently
long (>= 78 - 11 - 2) it's actually qp-encoded, due to how print_header
in mmime.c works.
(This affects, e.g., gmail, which seems to produce message-ids of length
68.)
Is this intended?
next prev parent reply other threads:[~2017-07-12 18:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-07 23:50 Wolfgang Jenkner
2017-07-08 18:49 ` Leah Neukirchen
2017-07-12 18:22 ` Wolfgang Jenkner [this message]
2017-07-12 19:12 ` Leah Neukirchen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ERNX3CSOLA.2VZMT4QLSH7WK@inode.at \
--to="wjen..."@inode.at \
--cc="le..."@vuxu.org \
--cc="mbl..."@googlegroups.com \
/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://git.vuxu.org/mblaze/
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 NNTP newsgroup(s).