From: Adrian Bunk <bunk@stusta.de>
To: Domen Puncer <domen@coderock.org>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [patch] maintainers: remove moderated arm list
Date: Mon, 3 Jan 2005 18:54:38 +0100 [thread overview]
Message-ID: <20050103175438.GL2980@stusta.de> (raw)
In-Reply-To: <20041225172155.A26504@flint.arm.linux.org.uk>
On Sat, Dec 25, 2004 at 05:21:55PM +0000, Russell King wrote:
> On Sat, Dec 25, 2004 at 06:08:25PM +0100, Domen Puncer wrote:
> > If you are subscribed to it, you already know the address. If you are not,
> > you probably don't want bounces.
>
> I don't particularly agree with this policy of removing such documentation,
> especially as I have a good reason to implement such policy on my mailing
> lists.
>
> If we must, I guess it's fine, but I expect *you* to provide the support
> to people to people who don't know where to go for it if *you* remove this.
I'm sometimes doing patches that cover many files, and I want to Cc the
patches to the developers in question.
If after sending 10 patches I get 5 "this is a subscribers-only list"
mails, I'm not going to subscribe to 5 lists, forward the patches to
them and unsubscribe again after this (and repeat this if there's some
discussion regarding one of these patches).
In my experience, the best solution is a list policy that allows
subscribers to post and requires moderator approval for non-members.
This policy that is already used by several lists listed in MAINTAINERS
is IMHO a good compromise between avoiding spam and allowing
non-subscribers to post to the list.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2005-01-03 17:57 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-25 17:08 [patch] maintainers: remove moderated arm list Domen Puncer
2004-12-25 17:21 ` Russell King
2004-12-25 17:34 ` Domen Puncer
2005-01-03 17:54 ` Adrian Bunk [this message]
2005-01-03 18:25 ` [patch] " Russell King
2005-01-04 17:33 ` Adrian Bunk
2005-01-05 12:52 ` Horst von Brand
2005-01-04 8:54 ` Erik Mouw
2005-01-04 9:00 ` Christoph Hellwig
2005-01-04 9:25 ` Russell King
2005-01-04 9:33 ` Christoph Hellwig
2005-01-04 10:19 ` Russell King
2005-01-05 9:20 ` Jes Sorensen
2005-01-05 14:04 ` Alan Cox
2005-01-06 9:20 ` Russell King
2005-01-04 21:13 ` Lee Revell
2005-01-05 0:07 ` Alan Cox
2005-01-05 1:19 ` Lee Revell
2005-01-04 22:03 ` Alan Cox
2005-01-04 9:08 ` Russell King
2005-01-04 9:37 ` Miles Bader
2005-01-04 9:48 ` Dave Airlie
2005-01-04 10:18 ` Erik Mouw
2005-01-04 13:05 ` Miles Bader
2005-01-04 13:37 ` Erik Mouw
2005-01-04 22:03 ` Alan Cox
2005-01-09 20:26 ` Pavel Machek
2004-12-26 16:50 ` Alan Cox
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=20050103175438.GL2980@stusta.de \
--to=bunk@stusta.de \
--cc=domen@coderock.org \
--cc=linux-kernel@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).