From: Pau Aliagas <linux4u@wanadoo.es>
To: <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.4.9-ac16
Date: Fri, 28 Sep 2001 09:03:30 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.33.0109280903030.2313-100000@pau.intranet.ct> (raw)
On Thu, 27 Sep 2001, Rik van Riel wrote:
> > 2.4.9-ac16
> > o Fix VM breakage from my merge error (Rik van Riel)
>
> This certainly explains the bad reports some people have sent
> in about 2.4.9-ac15 ;)
>
> Because of the now correct merge, I'm _very_ interested in
> any test results with this VM.
Performance is back to normality. I would say that it feels smoother, but
I haven't still stressed the system.
Pau
next reply other threads:[~2001-09-28 7:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-28 7:03 Pau Aliagas [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-09-27 17:51 Linux 2.4.9-ac16 Alan Cox
2001-09-27 18:26 ` Udo A. Steinberg
2001-09-27 18:28 ` Rik van Riel
2001-09-27 19:03 ` Tom Rini
2001-09-27 23:06 ` Alan Cox
2001-09-27 23:11 ` Tom Rini
2001-09-27 19:31 ` Kent Borg
2001-09-28 15:30 ` Stefan Becker
2001-09-28 16:39 ` Rik van Riel
2001-09-28 17:15 ` Tim Connors
2001-09-28 20:52 ` Russell King
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=Pine.LNX.4.33.0109280903030.2313-100000@pau.intranet.ct \
--to=linux4u@wanadoo.es \
--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;
as well as URLs for NNTP newsgroup(s).