From: "Konstantin Ryabitsev" <konstantin@linuxfoundation.org>
To: Rob Herring <robh@kernel.org>
Cc: users@linux.kernel.org, tools@linux.kernel.org
Subject: Re: [kernel.org users] b4 v0.4.0 available with new features
Date: Mon, 27 Jul 2020 10:52:23 -0400 [thread overview]
Message-ID: <20200727145223.sb3juyxu3jjrcn5m@chatter.i7.local> (raw)
In-Reply-To: <CAL_Jsq+8Ey7CHMObBNTd-EVSkNRca+DrWSABMgEctJjq-BsOGA@mail.gmail.com>
On Tue, Jun 09, 2020 at 04:24:29PM -0600, Rob Herring wrote:
> > > On Wed, May 06, 2020 at 02:23:16PM -0500, Rob Herring wrote:
> > > > I found a minor issue on patches with no 'To' header. They end up with
> > > > this:
> > > >
> > > > To: unlisted-recipients: no To-header on input <;
> > > >
> > > > However, that appears to be a public-inbox problem as it's on there
> > > > too. Here's an example[1].
> > >
> > > Interesting. I'm not seeing any strange output from that series. "b4 am"
> > > and "b4 ty" seem to be generating proper things.
> >
> > Yes, 'b4 am' is correct, but 'b4 mbox' is not. That's with 0.4.2.
>
> This is still an issue for me. I'm on current master, commit
> ca902b59c3d1 ("Fix mbox naming inconsistencies").
The reason I haven't really done anything about it is because we
currently don't do anything at all to messages retrieved via "b4 mbox"
(as opposed to "b4 am"). We just grab them as-is from public-inbox, and
that's how those messages are in the archive:
https://lore.kernel.org/linux-devicetree/20200506010809.6348-2-i.mikhaylov@yadro.com/raw
As far as I can tell, this is inserted by some MTA even before it gets
to vger, as it shows up in other public archives that I could find. The
MUAs should properly deal with this situation, so my current approach is
to treat this as "broken as designed".
-K
prev parent reply other threads:[~2020-07-27 14:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-24 17:04 b4 v0.4.0 available with new features Konstantin Ryabitsev
2020-04-24 23:35 ` [tools] " Martin K. Petersen
2020-04-27 18:40 ` Konstantin Ryabitsev
2020-04-28 2:12 ` Martin K. Petersen
2020-04-28 15:16 ` Konstantin Ryabitsev
2020-04-29 3:25 ` Martin K. Petersen
2020-04-28 16:03 ` [kernel.org users] " Jason Gunthorpe
2020-05-04 17:09 ` [kernel.org users] " Rob Herring
2020-05-04 17:17 ` Jason Gunthorpe
2020-05-04 20:09 ` Konstantin Ryabitsev
2020-05-04 23:07 ` Jason Gunthorpe
2020-05-04 20:03 ` Konstantin Ryabitsev
2020-05-04 22:58 ` Jason Gunthorpe
2020-05-04 23:04 ` Rob Herring
2020-05-06 19:23 ` Rob Herring
2020-05-07 20:20 ` Konstantin Ryabitsev
2020-05-12 19:07 ` Rob Herring
2020-06-09 22:24 ` Rob Herring
2020-07-27 14:52 ` 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=20200727145223.sb3juyxu3jjrcn5m@chatter.i7.local \
--to=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).