From: Alejandro Bonilla <abonilla@linuxwireless.org>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Blaisorblade <blaisorblade@yahoo.it>,
LKML <linux-kernel@vger.kernel.org>,
Andrian Bunk <bunk@stusta.de>, "H. Peter Anvin" <hpa@zytor.com>,
torvalds@osdl.org
Subject: Re: Giving developers clue how many testers verified certain kernel version
Date: Fri, 22 Jul 2005 21:15:14 -0500 [thread overview]
Message-ID: <42E1A832.7010604@linuxwireless.org> (raw)
In-Reply-To: <1122088160.6510.7.camel@mindpipe>
Lee Revell wrote:
>On Fri, 2005-07-22 at 20:07 -0500, Alejandro Bonilla wrote:
>
>
>>I will get flames for this, but my laptop boots faster and sometimes
>>responds faster in 2.4.27 than in 2.6.12. Sorry, but this is the fact
>>for me. IBM T42.
>>
>>
>
>Sorry dude, but there's just no way that any automated process can catch
>these.
>
>
I'm not looking for an automated process for this. But for all in
general, when moving from 2.6.11 to 2.6.12 or from any version to
another. (At least in the same kernel branch)
>You will have to provide a detailed bug report (with numbers) like
>everyone else so we can fix it. "Waiting for it to fix itself" is the
>WORST thing you can do.
>
>
I never do this, believe me, but I could if I don't really see a
problem. But there could really be one behind.
>If you find a regression vs. an earlier kernel, please assume that
>you're the ONLY one to notice it and respond accordingly.
>
>
OK, I will, but I first of all need to learn how to tell if benchmarks
are better or worse.
>Lee
>
>
>
.Alejandro
next prev parent reply other threads:[~2005-07-23 3:16 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-23 0:44 Giving developers clue how many testers verified certain kernel version Blaisorblade
2005-07-23 0:50 ` David Lang
2005-07-23 0:59 ` H. Peter Anvin
2005-07-23 1:07 ` Alejandro Bonilla
2005-07-23 3:09 ` Lee Revell
2005-07-23 2:15 ` Alejandro Bonilla [this message]
2005-07-23 3:21 ` Lee Revell
2005-07-23 2:34 ` Alejandro Bonilla
2005-07-23 3:31 ` Linus Torvalds
2005-07-23 2:40 ` Alejandro Bonilla
2005-07-23 3:34 ` Lee Revell
2005-07-23 9:05 ` Con Kolivas
2005-07-23 16:45 ` Lee Revell
2005-07-23 5:34 ` Giving developers clue how many testers verifiedcertain " Al Boldi
2005-07-23 3:56 ` Giving developers clue how many testers verified certain " Adrian Bunk
2005-07-23 9:21 ` Jesper Krogh
-- strict thread matches above, loose matches on Subject: below --
2005-07-22 1:34 Martin MOKREJŠ
2005-07-22 2:10 ` Mark Nipper
2005-07-22 2:38 ` Martin MOKREJŠ
2005-07-22 2:40 ` Alejandro Bonilla
2005-07-22 23:22 ` Adrian Bunk
2005-07-22 23:11 ` Adrian Bunk
2005-07-24 18:45 ` Martin MOKREJŠ
2005-07-24 18:54 ` Adrian Bunk
2005-07-24 19:10 ` Martin MOKREJŠ
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=42E1A832.7010604@linuxwireless.org \
--to=abonilla@linuxwireless.org \
--cc=blaisorblade@yahoo.it \
--cc=bunk@stusta.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.com \
--cc=torvalds@osdl.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