From: Jes Sorensen <jes@wildopensource.com>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: Christoph Hellwig <hch@infradead.org>,
Erik Mouw <erik@harddisk-recovery.com>,
Adrian Bunk <bunk@stusta.de>, Domen Puncer <domen@coderock.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [patch] maintainers: remove moderated arm list
Date: 05 Jan 2005 04:20:07 -0500 [thread overview]
Message-ID: <yq0brc4kzaw.fsf@jaguar.mkp.net> (raw)
In-Reply-To: <20050104101921.C9409@flint.arm.linux.org.uk>
>>>>> "Russell" == Russell King <rmk+lkml@arm.linux.org.uk> writes:
Russell> On Tue, Jan 04, 2005 at 09:33:26AM +0000, Christoph Hellwig
Russell> wrote:
>> On Tue, Jan 04, 2005 at 09:25:15AM +0000, Russell King wrote: > In
>> that case, you can personally choose not to send mail there
>> anymore. > It's completely up to you. No one is forcing you to
>> send email to any > address.
>>
>> I don't plan to force anyone to do anything with their
>> mailinglists. But we shouldn't mention lists with stupid policies
>> as maintainer contacts.
Russell> As Alan has already pointed out, there's more to the
Russell> MAINTAINERS file than just pointing out to main line kernel
Russell> developers where to send their patches.
Maybe it's time to have an additional entry in MAINTAINERS then -
having fscked up lists listed in there equal to sane ones seems
completely inappropriate. Requiring broken lists to marked as 'this
list is b0rked, use it at your own leisure'. That would save users and
developers from having to deal with the side effects of these fscked
up lists.
Using your own argument, I don't care why a list is fscked, the fact
is it's fscked and I don't want to have to waste my time on it.
Cheers,
Jes
next prev parent reply other threads:[~2005-01-05 9:20 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 ` [patch] " Adrian Bunk
2005-01-03 18:25 ` 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 [this message]
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=yq0brc4kzaw.fsf@jaguar.mkp.net \
--to=jes@wildopensource.com \
--cc=bunk@stusta.de \
--cc=domen@coderock.org \
--cc=erik@harddisk-recovery.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+lkml@arm.linux.org.uk \
/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).