From: Joe Perches <joe@perches.com>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: linux-kernel@vger.kernel.org,
Ralf Ramsauer <ralf.ramsauer@oth-regensburg.de>
Subject: Re: MAINTAINERS: Marking internal distribution lists
Date: Fri, 11 Sep 2020 03:16:28 -0700 [thread overview]
Message-ID: <7e513eea8ecf7ff1379d7a87245915469784121c.camel@perches.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2009110811520.9220@felia>
On Fri, 2020-09-11 at 08:37 +0200, Lukas Bulwahn wrote:
> 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
At one time, those sorts of email addresses were called "exploders"
Perhaps mark them as such?
Maybe like:
L: megaraidlinux.pdl@broadcom.com (exploder for non-subscribers)
next prev parent reply other threads:[~2020-09-11 10:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-11 6:37 Lukas Bulwahn
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 [this message]
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=7e513eea8ecf7ff1379d7a87245915469784121c.camel@perches.com \
--to=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--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®