From: Konstantin Ryabitsev <konstantin.ryabitsev@linux.dev>
To: Paul Barker <paul@pbarker.dev>, tools@linux.kernel.org
Cc: Konstantin Ryabitsev <konstantin.ryabitsev@linux.dev>
Subject: Re: [patatt][PATCH v2] Handle MIME encoded-word & other header manglings
Date: Mon, 31 May 2021 11:12:47 -0400 [thread overview]
Message-ID: <162247394427.416221.8663625239721047804.b4-ty@linux.dev> (raw)
In-Reply-To: <20210531140539.7630-1-paul@pbarker.dev>
On Mon, 31 May 2021 15:05:39 +0100, Paul Barker wrote:
> When testing patatt with patches sent to a sr.ht hosted mailing list, it
> was found that long header lines (such as the X-Developer-Signature
> line) were re-encoded using the MIME encoded-word syntax (RFC 2047) when
> an mbox archive is generated, causing patatt to choke on the resulting
> text which looks like this:
>
> X-Developer-Signature: v=1; a=openpgp-sha256; l=672; h=from:subject;
> bh=C40yOKgIfnNIUP+OW9WyPdBfljkZPpfUL1NepOODlx8=; =?utf-8?q?b=3DowGbwMvMwCF2?=
> =?utf-8?q?w7xIXuiX9CvG02pJDAmb67lTNi0+IeF97TL76vtKD7xjSjaluz0o/KfmZLX8rMi7_?=
> =?utf-8?q?l3M6O0pZGMQ4GGTFFFl2z951+fqDJVt7b0gHw8xhZQIZwsDFKQATydFhZJi+fFfvJ?=
> =?utf-8?q?8+0MF7GrfzWnP?=
> K7mAM/3n/r/UC+bprf6/g114QYGdbHcsaK7b1nanfA4IeZi1V0lL26cruXUWxgSEnNDP1FrAA=
>
> [...]
Applied, thanks!
[1/1] Handle MIME encoded-word & other header manglings
commit: 30840a6acae935ebc5332d08d61222cebe0b518b
Best regards,
--
Konstantin Ryabitsev <konstantin.ryabitsev@linux.dev>
prev parent reply other threads:[~2021-05-31 15:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-31 14:05 [patatt][PATCH v2] Handle MIME encoded-word & other header manglings Paul Barker
2021-05-31 15:12 ` Konstantin Ryabitsev [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=162247394427.416221.8663625239721047804.b4-ty@linux.dev \
--to=konstantin.ryabitsev@linux.dev \
--cc=paul@pbarker.dev \
--cc=tools@linux.kernel.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox