From: Chen-Yu Tsai <wenst@chromium.org>
To: David Woodhouse <dwmw2@infradead.org>
Cc: "Rob Herring" <robh@kernel.org>,
"Geert Uytterhoeven" <geert@linux-m68k.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>,
mark@msapiro.net, workflows@vger.kernel.org,
"Konstantin Ryabitsev" <konstantin@linuxfoundation.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"MTD Maling List" <linux-mtd@lists.infradead.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Arnd Bergmann" <arnd@arndb.de>,
"Miquel Raynal" <miquel.raynal@bootlin.com>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Subject: Re: Getting rid of infradead.org - corrupted subjects
Date: Tue, 14 Jun 2022 17:47:49 +0800 [thread overview]
Message-ID: <CAGXv+5EbA29qfd9WPP=hawxgAKE-tSQvCsjX+-a0hmUsmWFgzA@mail.gmail.com> (raw)
In-Reply-To: <6757109d4eb065682706e455c9772259cf11e557.camel@infradead.org>
On Wed, May 25, 2022 at 11:17 PM David Woodhouse <dwmw2@infradead.org> wrote:
>
> On Wed, 2022-05-25 at 09:30 -0500, Rob Herring wrote:
> >
> > Yay!!! I should have asked years ago...
> >
> >
> >
> > Any chance the appending of footers can be stopped as it causes lore
> > to report duplicates and b4 dmarc attestation to fail?
>
> That's up to individual list owners; it's part of the per-list config.
> It's very easy to turn off.
Could you share who the owners for linux-arm-kernel@, linux-mtd@ and
linux-mediatek@, just to name a few, are?
Thanks
ChenYu
next prev parent reply other threads:[~2022-06-14 9:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-25 8:07 Getting rid of infradead.org - corrupted subjects Krzysztof Kozlowski
2022-05-25 8:34 ` Geert Uytterhoeven
2022-05-25 9:55 ` David Woodhouse
2022-05-25 14:30 ` Rob Herring
2022-05-25 15:16 ` David Woodhouse
2022-06-14 9:47 ` Chen-Yu Tsai [this message]
2022-05-25 19:23 ` Uwe Kleine-König
2022-05-31 19:59 ` Uwe Kleine-König
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='CAGXv+5EbA29qfd9WPP=hawxgAKE-tSQvCsjX+-a0hmUsmWFgzA@mail.gmail.com' \
--to=wenst@chromium.org \
--cc=arnd@arndb.de \
--cc=dwmw2@infradead.org \
--cc=geert@linux-m68k.org \
--cc=konstantin@linuxfoundation.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=mark@msapiro.net \
--cc=miquel.raynal@bootlin.com \
--cc=robh@kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
--cc=workflows@vger.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).