From: Mikael Pettersson <mikpe@it.uu.se>
To: Ingo Molnar <mingo@elte.hu>
Cc: Mikael Pettersson <mikpe@it.uu.se>,
Tino Keitel <tino.keitel@gmx.de>,
linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: 2.6.24 regression: Wake On Lan in sky2 broken on Mac mini
Date: Mon, 28 Jan 2008 14:37:38 +0100 [thread overview]
Message-ID: <18333.55970.74841.660462@harpo.it.uu.se> (raw)
In-Reply-To: <20080128125535.GE32496@elte.hu>
Ingo Molnar writes:
>
> * Mikael Pettersson <mikpe@it.uu.se> wrote:
>
> > > Now I tried the 2.6.24 release and noticed that WOL is still
> > > broken. I'll be happy to test any patches that can make it into
> > > 2.6.24.1.
> >
> > 1. Wrong mailing list; use netdev (@vger) instead.
>
> lkml is the right mailing list for reporting Linux bugs.
>
> this is an extermely harmful trend i've seen lately: some kernel hackers
> going out on a limb directing the flow of bugreports _away_ from lkml,
> by suggesting to testers that lkml is somehow inappropriate for
> reporting Linux kernel bugs.
>
> It's not even the standard "I Cc:-ed netdev, maybe they are interested
> in this" message but the above, plain incorrect: "this is the wrong
> mailing list" message.
>
> Mikael, what you do is as harmful to Linux as if you were intentionally
> putting bugs into the kernel source. In fact it's more harmful because
> it is irreversible: bugs you put into Linux i can fix and i can review
> all past patches you did to undo the damage - tester attention and
> feedback you redirect we cannot direct back.
Ok, I can see how my overly terse statement could be interpreted
in this way, and I apologize for that.
However, it _is_ a fact that there is a proliferation of specialized
mailing lists, and it is also a fact that many developers _only_ read
those lists. I'm in no way defending this behaviour, on the contrary
I probably dislike it as much as you do. But we can't ignore it.
I should of course have written something like "please cc: <whateverlist>"
instead of the stupid "wrong mailing" list comment.
> Stop it!
Gladly.
next prev parent reply other threads:[~2008-01-28 13:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-28 0:29 Tino Keitel
2008-01-28 8:21 ` Mikael Pettersson
2008-01-28 8:48 ` Tino Keitel
2008-01-28 15:59 ` Stephen Hemminger
2008-01-28 12:55 ` Ingo Molnar
2008-01-28 13:37 ` Mikael Pettersson [this message]
2008-01-28 13:43 ` Tino Keitel
2008-01-28 14:12 ` Adrian Bunk
2008-01-28 15:22 ` Rafael J. Wysocki
2008-01-28 16:11 ` Ingo Molnar
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=18333.55970.74841.660462@harpo.it.uu.se \
--to=mikpe@it.uu.se \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tino.keitel@gmx.de \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®