From: Lukas Bulwahn <lukas.bulwahn@gmail.com>
To: Joe Perches <joe@perches.com>
Cc: linux-kernel@vger.kernel.org,
Ralf Ramsauer <ralf.ramsauer@oth-regensburg.de>
Subject: MAINTAINERS: Marking internal distribution lists
Date: Fri, 11 Sep 2020 08:37:54 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.2009110811520.9220@felia> (raw)
Hi Joe,
in my continued effort to clean up MAINTAINERS, I came across various
email "lists" that are actually just some kind of internal distribution
lists, but we cannot subscribe to them (no archives available) and they
are not affiliated to a specific person.
Some examples are:
- bcm-kernel-feedback-list.broadcom.com
- brcm80211-dev-list.cypress.com
- brcm80211-dev-list.pdl.broadcom.com
- coreteam.netfilter.org
- esc.storagedev.microsemi.com
- linux-imx.nxp.com
- megaraidlinux.pdl.broadcom.com
- MPT-FusionLinux.pdl.broadcom.com
- ocfs2-devel.oss.oracle.com
- oss-drivers.netronome.com
- patches.opensource.cirrus.com
- qat-linux.intel.com
- rds-devel.oss.oracle.com
- sparmaintainer.unisys.com
- wil6210.qti.qualcomm.com
- x86.kernel.org
One of the dots needs to be replaced by an @, of course, but let us not
make it too easy for spammers to pick something up ;)
Some of them are mentioned in MAINTAINERS with 'L:' entry as those above,
some others are mentioned in MAINTAINERS with an 'R:' or even a 'M:' entry.
Greg KH also called them email group aliases and does not want them to be
valid entries for maintainer roles ('M:') because it is unclear who really
is the maintainer for such sections (when is it orphaned, when does the
maintainer actually change, etc.).
Would you have any recommendation for marking/handling such email
addresses in MAINTAINERS?
I thought about the following options:
If the email address cannot be affiliated to one specific person and the
list is not subscribable,
A. should we then mark them as 'L: email (internal)'? (or
some other keyword, such as non-subscribable, restricted group...)
B. should we just make them 'R:' entries?
With a bit of searching and guessing, I can probably update all those
entries in MAINTAINERS and pass them to the according mailing lists for
review and inclusion.
Best regards,
Lukas
next reply other threads:[~2020-09-11 6:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-11 6:37 Lukas Bulwahn [this message]
2020-09-11 9:46 ` Christoph Hellwig
2020-09-11 10:12 ` Lukas Bulwahn
2020-09-11 14:40 ` Martin K. Petersen
2020-09-11 10:16 ` Joe Perches
2020-09-11 10:23 ` Lukas Bulwahn
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=alpine.DEB.2.21.2009110811520.9220@felia \
--to=lukas.bulwahn@gmail.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ralf.ramsauer@oth-regensburg.de \
/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
all inboxes | Powered by JetHome®