From: Eric Miao <eric.y.miao@gmail.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
linux-arm-kernel@lists.arm.linux.org.uk,
kernel list <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: Mailing List Etiquette
Date: Fri, 21 Aug 2009 23:16:10 +0800 [thread overview]
Message-ID: <4A8EBA3A.6080205@gmail.com> (raw)
In-Reply-To: <20090821090546.GI8431@elf.ucw.cz>
Pavel Machek wrote:
> On Fri 2009-08-21 09:39:53, Russell King - ARM Linux wrote:
>> On Fri, Aug 21, 2009 at 10:30:28AM +0200, Pavel Machek wrote:
>>> On Fri 2009-08-21 09:18:49, Russell King - ARM Linux wrote:
>>>> Right, this does it. I'm off on holiday as of now.
>>> Cool.
>>>
>>>> Guess what? I've had enough of this crap. I'm pulling the plug on
>>>> these lists. Everyone, you know the email address to complain to.
>>>> One community killed by an "open list" zealot.
>>> If you are not willing to keep information up to date, don't spam with
>>> it. It is as simple as that. I'm looking forward to list administrator
>>> who does not go ballistic every time problem is reported with his
>>> list, and the one who does not call me names.
>> Your constant whinging is the reason for the action which has now been
>> taken. The lists are now off line until future notice, when I can deal
>> with the crap that constantly pours out of your keyboard.
>
> So perhaps following patch is in order?
> Pavel
>
Is everyone happy now? Can't we just solve the problem in a more elegant
way instead of irritating each other and showing disrespect?
I've been working on ARM-list for several years, there is some trivial
issues, nothing is perfect, but I found it working quite well and is
well managed. Russell has invested a lot effort in making this happen
indeed in the past several years, and someone need to see this fact.
Let's have more considerations for him: what if you are forced to
change something you've devoted much in, and even with some difficult
and hard-to-tell reasons?
Well, I mean if there are really good reasons to move over to vger,
the vast majority of the ARM community would have already moved there,
there must be some values within the ARM-list.
It's OK there are some requirements to make this ML more open and
works more like other ML on vger, but this thread apparently, shows
a bad way to solve problems.
And I don't like the patch, it doesn't solve any problem. Leaving for
each subsystem maintainers to make the choice will be a better idea
to me.
next prev parent reply other threads:[~2009-08-21 15:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090819060004.GA23859@n2100.arm.linux.org.uk>
2009-08-21 7:26 ` Mailing List Etiquette Pavel Machek
2009-08-21 7:28 ` Pavel Machek
2009-08-21 8:06 ` Marek Vasut
2009-08-21 8:18 ` Russell King - ARM Linux
2009-08-21 8:30 ` Pavel Machek
2009-08-21 8:39 ` Russell King - ARM Linux
2009-08-21 8:55 ` David Miller
2009-08-21 14:54 ` Theodore Tso
2009-08-21 15:54 ` Bartlomiej Zolnierkiewicz
2009-08-21 9:05 ` Pavel Machek
2009-08-21 15:16 ` Eric Miao [this message]
2009-08-24 5:15 ` Miles Bader
2009-08-21 9:45 ` [PATCH] MAINTAINERS: ARM lists moved to vger.kernel.org Joe Perches
2009-08-21 11:54 ` Mikael Pettersson
2009-08-21 14:39 ` Joe Perches
2009-08-21 14:54 ` Martin Bogomolni
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=4A8EBA3A.6080205@gmail.com \
--to=eric.y.miao@gmail.com \
--cc=akpm@osdl.org \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=pavel@ucw.cz \
/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