From: Rene Herman <rene.herman@gmail.com>
To: Geoff Levand <geoffrey.levand@am.sony.com>
Cc: Joe Perches <joe@perches.com>,
cbe-oss-dev-owner@ozlabs.org,
Satyam Sharma <satyam@infradead.org>,
Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>,
Linux Kernel Development <linux-kernel@vger.kernel.org>,
Cell Broadband Engine OSS Development <cbe-oss-dev@ozlabs.org>,
mokuno@sm.sony.co.jp
Subject: Re: [PATCH] PS3: Update MAINTAINERS
Date: Tue, 21 Aug 2007 22:33:16 +0200 [thread overview]
Message-ID: <46CB4C0C.70901@gmail.com> (raw)
In-Reply-To: <46CB4862.9020601@am.sony.com>
On 08/21/2007 10:17 PM, Geoff Levand wrote:
> Rene Herman wrote:
>> On 08/21/2007 10:01 PM, Joe Perches wrote:
>>> The reason it is being held:
>>>
>>> Post by non-member to a members-only list
>> That means it's not a subcriber-only list -- the message wasn't rejected,
>> just subjected to moderation.
>>
>
> So maybe it would be more precise to have something like this:
>
> -L: cbe-oss-dev@ozlabs.org
> +L: cbe-oss-dev@ozlabs.org (moderated)
Perhaps. In these spamridden days, mailinglists that don't have the kind of
(human and other) resources behind them that linux-kernel has basically have
the choice between drowning in spam, becoming subscriber only or moderate
non-subscribers and of these, that third option is "best among the bad".
alsa-devel for example also went this route -- the spam levels simply
weren't tolerable anymore for any subscriber and the list was dying as a
result. Moderation sucks, but subcriber-only sucks even worse (generally,
and/but even more so for lists that expect crossposts from linux-kernel) so
what's a small-time list to do.
Moderation takes some effort so the lists that moderate have made the
explicit choice to not become subscriber-only. While subscriber-only
certainly is useful to mention alongside the list address itself, I'm not
too sure mentioning moderation makes a great deal of sense actually -- if
all's well, the moderator will simply approve it and you don't have to deal
with it other than that.
Rene.
next prev parent reply other threads:[~2007-08-21 20:38 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-16 11:20 [PATCH 000 of 6] A few block-layer tidy-up patches NeilBrown
2007-08-16 11:20 ` [PATCH 001 of 6] Merge blk_recount_segments into blk_recalc_rq_segments NeilBrown
2007-08-16 11:21 ` [PATCH 002 of 6] Introduce rq_for_each_segment replacing rq_for_each_bio NeilBrown
2007-08-17 7:13 ` Geert Uytterhoeven
2007-08-18 14:37 ` Satyam Sharma
2007-08-18 14:30 ` Jan Engelhardt
2007-08-18 14:48 ` Satyam Sharma
2007-08-20 11:21 ` Geert Uytterhoeven
2007-08-20 12:46 ` Jan Engelhardt
2007-08-21 1:38 ` Satyam Sharma
2007-08-21 7:09 ` Geert Uytterhoeven
2007-08-21 9:46 ` Satyam Sharma
2007-08-21 9:52 ` Geert Uytterhoeven
2007-08-21 10:41 ` [PATCH] PS3: Update MAINTAINERS Satyam Sharma
2007-08-21 19:01 ` Geoff Levand
2007-08-21 20:01 ` Joe Perches
2007-08-21 20:06 ` Rene Herman
2007-08-21 20:17 ` Geoff Levand
2007-08-21 20:33 ` Rene Herman [this message]
2007-08-21 20:48 ` Satyam Sharma
2007-08-21 20:41 ` Rene Herman
2007-08-21 20:47 ` Joe Perches
2007-08-21 21:58 ` Hugh Blemings
2007-08-23 18:14 ` Matt Mackall
2007-08-24 5:52 ` Hugh Blemings
2007-08-21 20:10 ` Geoff Levand
2007-08-24 6:25 ` [Cbe-oss-dev] " Hugh Blemings
2007-08-24 6:47 ` Satyam Sharma
2007-08-24 6:48 ` Hugh Blemings
2007-08-16 11:21 ` [PATCH 003 of 6] Fix various abuse of bio fields in umem.c NeilBrown
2007-08-16 11:21 ` [PATCH 004 of 6] New function blk_req_append_bio NeilBrown
2007-08-16 11:21 ` NeilBrown
2007-08-16 11:21 ` [PATCH 005 of 6] Stop exporting blk_rq_bio_prep NeilBrown
2007-08-16 11:21 ` NeilBrown
2007-08-16 11:21 ` [PATCH 006 of 6] Share code between init_request_from_bio and blk_rq_bio_prep NeilBrown
2007-08-16 11:36 ` [PATCH 000 of 6] A few block-layer tidy-up patches Jens Axboe
2007-08-17 0:40 ` Neil Brown
2007-08-17 6:17 ` Jens Axboe
2007-08-17 7:21 ` Neil Brown
2007-08-17 12:37 ` Jens Axboe
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=46CB4C0C.70901@gmail.com \
--to=rene.herman@gmail.com \
--cc=Geert.Uytterhoeven@sonycom.com \
--cc=cbe-oss-dev-owner@ozlabs.org \
--cc=cbe-oss-dev@ozlabs.org \
--cc=geoffrey.levand@am.sony.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mokuno@sm.sony.co.jp \
--cc=satyam@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.