From: "James Bottomley" <James.Bottomley@HansenPartnership.com>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
Rob Herring <robh@kernel.org>
Cc: tools@linux.kernel.org, users@linux.kernel.org
Subject: Re: [kernel.org users] b4 v0.3.4 released
Date: Thu, 26 Mar 2020 09:27:38 -0700 [thread overview]
Message-ID: <1585240058.3610.19.camel@HansenPartnership.com> (raw)
In-Reply-To: <20200326161622.pzma44m6vte2qi33@chatter.i7.local>
On Thu, 2020-03-26 at 12:16 -0400, Konstantin Ryabitsev wrote:
> On Thu, Mar 26, 2020 at 10:11:44AM -0600, Rob Herring wrote:
> > > I'm seeing corruption of the subject on patches[1] with a comma
> > > in the subject (and I'd guess only ones longer than 70 something
> > > chars). It's fine on lore web interface, but it gets wrapped in
> > > the downloaded mbox. A log is attached. When it gets applied, a
> > > space is inserted after the comma:
> > >
> > > dt-bindings: iio/accel: Drop duplicate adi, adxl345/6 from
> > > trivial-devices.yaml
> >
> > Nevermind. It's not b4, but the dri-devel list that is corrupting
> > the subject.
> >
> > https://lore.kernel.org/dri-devel/20200325220542.19189-2-robh@kerne
> > l.org/
> > https://lore.kernel.org/linux-devicetree/20200325220542.19189-2-rob
> > h@kernel.org/
>
> I think it's actually Python's fault. I'm trying to isolate the
> operation that causes it. It makes sense that dri-devel also
> exhibits it, because it's a mailman-managed list.
It smells like a mishandling of RFC2822 header folding rules.
https://tools.ietf.org/html/rfc2822#section-2.2.3
Lots of email tools get this wrong as well, so they add an extra space
where the subject header got split by the wrapping because they expect
the header to split at a space and the space to be eaten by the split,
but that's not what the rules say.
James
next prev parent reply other threads:[~2020-03-26 16:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-23 22:20 b4 v0.3.4 released Konstantin Ryabitsev
2020-03-25 2:11 ` [kernel.org users] " Jason A. Donenfeld
2020-03-25 2:19 ` Jason A. Donenfeld
2020-03-25 15:05 ` Konstantin Ryabitsev
2020-03-25 15:26 ` Konstantin Ryabitsev
2020-03-26 16:04 ` Rob Herring
2020-03-26 16:11 ` Rob Herring
2020-03-26 16:16 ` Konstantin Ryabitsev
2020-03-26 16:27 ` James Bottomley [this message]
2020-03-26 16:31 ` Geert Uytterhoeven
[not found] ` <15FFE6D3B979AF4C.32445@linux.kernel.org>
2020-03-26 16:32 ` Konstantin Ryabitsev
2020-03-26 20:18 ` Jason A. Donenfeld
2020-03-27 18:15 ` Konstantin Ryabitsev
2020-04-06 21:53 ` Konstantin Ryabitsev
2020-09-22 22:17 ` Rob Herring
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=1585240058.3610.19.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=konstantin@linuxfoundation.org \
--cc=robh@kernel.org \
--cc=tools@linux.kernel.org \
--cc=users@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;
as well as URLs for NNTP newsgroup(s).