From: joe@perches.com (Joe Perches)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] MAINTAINERS: Move ARM lists to infradead
Date: Wed, 16 Sep 2009 13:13:58 -0700 [thread overview]
Message-ID: <1253132038.10465.5.camel@Joe-Laptop.home> (raw)
In-Reply-To: <m3d45qpsgl.fsf@intrepid.localdomain>
On Wed, 2009-09-16 at 22:03 +0200, Krzysztof Halasa wrote:
> Joe Perches <joe@perches.com> writes:
> > I believe it's still moderated.
> Does that matter to the point we have to put it in the file?
> Non-spam from non-subscribers passes through, right? The "moderated for
> non-subscribers" suggests that one should subscribe prior to posting,
> which is IMHO not the case.
I don't much care which is selected, but I think it's clear
moderated doesn't mean subscribers-only.
"moderated for non-subscribers" means there might be a
rejection or a delay before a message is forwarded to a list.
Here are the lists that are marked "moderated" in MAINTAINERS
$ grep moderated MAINTAINERS | sort | uniq
L: alsa-devel at alsa-project.org (moderated for non-subscribers)
L: bluesmoke-devel at lists.sourceforge.net (moderated for non-subscribers)
L: linux-am33-list at redhat.com (moderated for non-subscribers)
L: linux-fbdev-devel at lists.sourceforge.net (moderated for non-subscribers)
L: linux-geode at lists.infradead.org (moderated for non-subscribers)
L: linux-zigbee-devel at lists.sourceforge.net (moderated for non-subscribers)
L: ocfs2-devel at oss.oracle.com (moderated for non-subscribers)
L: rds-devel at oss.oracle.com (moderated for non-subscribers)
L: tpmdd-devel at lists.sourceforge.net (moderated for non-subscribers)
next prev parent reply other threads:[~2009-09-16 20:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-16 16:09 [PATCH] MAINTAINERS: Move ARM lists to infradead Joe Perches
2009-09-16 18:10 ` Sebastian Andrzej Siewior
2009-09-16 18:16 ` Joe Perches
2009-09-16 20:03 ` Krzysztof Halasa
2009-09-16 20:13 ` Joe Perches [this message]
2009-09-17 7:52 ` Sebastian Andrzej Siewior
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=1253132038.10465.5.camel@Joe-Laptop.home \
--to=joe@perches.com \
--cc=linux-arm-kernel@lists.infradead.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