From: "Paolo Ciarrocchi" <ciarrocchi@linuxmail.org>
To: <ahu@ds9a.nl>
Cc: linux-kernel@vger.kernel.org, andrea@suse.de
Subject: Re: BYTE UNIX Benchmarks (Version 4.1.0)
Date: Fri, 06 Sep 2002 20:09:14 +0800 [thread overview]
Message-ID: <20020906120914.23405.qmail@linuxmail.org> (raw)
From: bert hubert <ahu@ds9a.nl>
> Can you tell us what the 'baseline' is and what the 'result' is? Ie, which
> kernels.
Oh yes, I wrote it in the privious email when linuxmail.org started to mangle my emails (now is all ok).
Result is 2.4.20-pre5aa1.
The baseline is a vanilla 2.4.19
In my first email there is the result of 2.5.33 baseline 2.4.19
Ciao,
Paolo
--
Get your free email from www.linuxmail.org
Powered by Outblaze
next reply other threads:[~2002-09-06 12:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-06 12:09 Paolo Ciarrocchi [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-09-06 7:52 BYTE UNIX Benchmarks (Version 4.1.0) Paolo Ciarrocchi
2002-09-06 11:57 ` bert hubert
2002-09-06 7:41 Paolo Ciarrocchi
2002-09-05 22:34 Paolo Ciarrocchi
2002-09-05 22:09 Paolo Ciarrocchi
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=20020906120914.23405.qmail@linuxmail.org \
--to=ciarrocchi@linuxmail.org \
--cc=ahu@ds9a.nl \
--cc=andrea@suse.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