From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: workflows@vger.kernel.org,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: "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: Getting rid of infradead.org - corrupted subjects
Date: Wed, 25 May 2022 10:07:03 +0200 [thread overview]
Message-ID: <b36280be-9993-9a78-0960-4094efeed1aa@linaro.org> (raw)
Hi all,
The address list is semi-random as I don't know whom to approach.
Problem: infradead.org corrupts email subjects by changing:
s/,/, /
Examples:
1. Previous discussion with Uwe about linux-arm-kernel:
https://lore.kernel.org/all/20220215125856.es2euyoqo6mp4y2t@pengutronix.de/
2. My last email for MTD
Modified email:
https://lore.kernel.org/linux-mtd/20220408063720.12826-1-krzysztof.kozlowski@linaro.org/
Proper email:
https://lore.kernel.org/all/3e550deb-7c27-894b-a0b5-62609a60f17f@microchip.com/
When people use Patchwork or b4, the email from the list is being used,
thus the one with a changed subject. Example:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9547c4e74f6b4b56c2f9e4e7a286ce126fd333fa
The subject should be "dt-bindings: mtd: jedec,spi-nor: remove unneeded
properties" (no space after coma)
This leads to real commits with a bit odd subject. At least not the
original subject.
Can we do something about infradead? Get rid of it and move the mailing
lists to vger.kernel.org? Or fix it?
Best regards,
Krzysztof
next reply other threads:[~2022-05-25 8:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-25 8:07 Krzysztof Kozlowski [this message]
2022-05-25 8:34 ` Getting rid of infradead.org - corrupted subjects 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
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=b36280be-9993-9a78-0960-4094efeed1aa@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=arnd@arndb.de \
--cc=konstantin@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--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).