From: Andi Kleen <andi@firstfloor.org>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Daniel Hazelton <dhazelton@enter.net>,
"Parag Warudkar" <parag.warudkar@gmail.com>,
"Adrian Bunk" <bunk@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: How to reduce the number of open kernel bugs
Date: Fri, 02 May 2008 20:18:03 +0200 [thread overview]
Message-ID: <877iecvack.fsf@basil.nowhere.org> (raw)
In-Reply-To: <200805021948.48345.rjw@sisk.pl> (Rafael J. Wysocki's message of "Fri, 2 May 2008 19:48:47 +0200")
"Rafael J. Wysocki" <rjw@sisk.pl> writes:
>>
>> And I have to agree here. But there should be something that can be done
>> to "coax" the maintainers that pull that kind of immature crap into acting
>> mature and responsible.
>
> Well, how exactly would you want to do that?
He could start to fix a few such bugs he's describing (usually with
very vague reports) by himself. Or instead of fixing them just trying
to get all the information out of the reporter. Then he would realize
what the the difference between theory and practice is.
-Andi
next prev parent reply other threads:[~2008-05-02 18:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-02 14:42 How to reduce the number of open kernel bugs Parag Warudkar
2008-05-02 15:11 ` Adrian Bunk
2008-05-02 16:29 ` Daniel Hazelton
2008-05-02 17:27 ` Andi Kleen
2008-05-02 17:40 ` Daniel Hazelton
2008-05-02 17:30 ` Parag Warudkar
2008-05-02 17:44 ` Daniel Hazelton
2008-05-02 17:48 ` Rafael J. Wysocki
2008-05-02 18:18 ` Andi Kleen [this message]
2008-05-02 23:10 ` Daniel Hazelton
2008-05-02 18:01 ` Adrian Bunk
2008-05-02 18:25 ` Parag Warudkar
2008-05-02 23:15 ` Daniel Hazelton
-- strict thread matches above, loose matches on Subject: below --
2008-05-02 12:42 Adrian Bunk
2008-05-03 10:13 ` SL Baur
2008-05-03 11:21 ` Adrian Bunk
2008-05-03 12:00 ` SL Baur
2008-05-03 15:43 ` Stefan Richter
2008-05-03 15:48 ` Stefan Richter
2008-05-05 18:12 ` Adrian Bunk
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=877iecvack.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=bunk@kernel.org \
--cc=dhazelton@enter.net \
--cc=linux-kernel@vger.kernel.org \
--cc=parag.warudkar@gmail.com \
--cc=rjw@sisk.pl \
/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