From: "Kok, Auke" <auke-jan.h.kok@intel.com>
To: devzero@web.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: RFC: starting a kernel-testers group for newbies
Date: Thu, 01 May 2008 09:26:59 -0700 [thread overview]
Message-ID: <4819EF53.6090808@intel.com> (raw)
In-Reply-To: <261643149@web.de>
devzero@web.de wrote:
>> I'll try to do this:
>> - create some Wiki page
>> - get a mailing list at vger
>> - point newbies to this mailing list
>> - tell people there which kernels to test
>> - figure out and document stuff like how to bisect between -next kernels
>> - help them to do whatever is required for a proper bug report
>
> good idea :)
>
> one more:
> reported bugs sometimes get lost in lkml (or elsewhere) and may not get the attention they need.
>
> maybe there are not enough people who put some steadiness into tracking bugs (i.e. put them in bugzilla and make sure they get tracked/resolved) ?
I would say that this should be one of the main goals - have a team of people who
can consistently be assigned bugs for duplication and verification. Getting newly
opened bugs reproduced can be half the solution (and a great way to learn the
kernel on the side).
often the reporter of the bug never confirms that the bug is fixed - another place
where linux testers can help out...
Auke
next prev parent reply other threads:[~2008-05-01 16:28 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-01 16:11 RFC: starting a kernel-testers group for newbies devzero
2008-05-01 16:26 ` Kok, Auke [this message]
2008-05-01 17:12 ` Adrian Bunk
-- strict thread matches above, loose matches on Subject: below --
2008-05-01 17:09 devzero
2008-05-01 17:27 ` Steven Rostedt
2008-05-01 16:36 devzero
2008-04-30 2:03 Slow DOWN, please!!! David Miller
2008-04-30 19:36 ` Rafael J. Wysocki
2008-04-30 20:15 ` Andrew Morton
2008-04-30 20:31 ` Linus Torvalds
2008-05-01 0:31 ` RFC: starting a kernel-testers group for newbies Adrian Bunk
2008-04-30 7:03 ` Arjan van de Ven
2008-05-01 8:13 ` Andrew Morton
2008-04-30 14:15 ` Arjan van de Ven
2008-05-01 12:42 ` David Woodhouse
2008-04-30 15:02 ` Arjan van de Ven
2008-05-05 10:03 ` Benny Halevy
2008-05-04 12:45 ` Rene Herman
2008-05-04 13:00 ` Pekka Enberg
2008-05-04 13:19 ` Rene Herman
2008-05-01 9:16 ` Frans Pop
2008-05-01 10:30 ` Enrico Weigelt
2008-05-01 13:02 ` Adrian Bunk
2008-05-01 11:30 ` Adrian Bunk
2008-04-30 14:20 ` Arjan van de Ven
2008-05-01 12:53 ` Rafael J. Wysocki
2008-05-01 13:21 ` Adrian Bunk
2008-05-01 15:49 ` Andrew Morton
2008-05-01 1:13 ` Arjan van de Ven
2008-05-02 9:00 ` Adrian Bunk
2008-05-01 16:38 ` Steven Rostedt
2008-05-01 17:18 ` Andrew Morton
2008-05-01 17:24 ` Theodore Tso
2008-05-01 19:26 ` Andrew Morton
2008-05-01 19:39 ` Steven Rostedt
2008-05-02 10:23 ` Andi Kleen
2008-05-02 2:08 ` Paul Mackerras
2008-05-02 3:10 ` Josh Boyer
2008-05-02 4:09 ` Paul Mackerras
2008-05-02 8:29 ` Adrian Bunk
2008-05-02 10:16 ` Paul Mackerras
2008-05-02 11:58 ` Adrian Bunk
2008-05-02 14:58 ` Linus Torvalds
2008-05-02 15:44 ` Carlos R. Mafra
2008-05-02 16:28 ` Linus Torvalds
2008-05-02 17:15 ` Carlos R. Mafra
2008-05-02 18:02 ` Pallipadi, Venkatesh
2008-05-09 16:32 ` Mark Lord
2008-05-09 19:30 ` Carlos R. Mafra
2008-05-09 20:39 ` Mark Lord
2008-05-01 0:41 ` David Miller
2008-05-01 13:23 ` 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=4819EF53.6090808@intel.com \
--to=auke-jan.h.kok@intel.com \
--cc=devzero@web.de \
--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