From: "Daniel E. Shipton" <dshipton@vrac.iastate.edu>
To: "Erik Ljungström" <insight@metalab.unc.edu>
Cc: Rene Rebe <rene.rebe@gmx.net>,
pabloa@laotraesquina.com.ar, mtopper@xarch.tu-graz.ac.at,
Ruth.Ivimey-Cook@ivimey.org, hahn@physics.mcmaster.ca,
linux-kernel@vger.kernel.org
Subject: Re: Request for 2.4.20 to be a non-trivial-bugfixes-only version
Date: 04 Apr 2002 00:02:53 -0600 [thread overview]
Message-ID: <1017900173.18439.10.camel@localhost.localdomain> (raw)
In-Reply-To: <20020402205918.36a94648.insight@metalab.unc.edu>
> What's wrong with the 2.4.17 kernel? I have'n had a better one since the 2.2.19 :)
I'm with you on that....i put it on one machine and threw away the
redhat rpm to find that i needed it a week later for another machine and
redhat had released their 2.4.18. So had to make it by hand for a
change. 2.4.17 does well at everything while not giving oopses.
also alan's 2.4.13 was really good too.
daniel.e.shipton
next prev parent reply other threads:[~2002-04-04 6:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.33.0203291601040.3565-100000@coffee.psychology. mcmaster.ca>
2002-03-29 21:26 ` Request for 2.4.20 to be a non-trivial-bugfixes-only version Ruth Ivimey-Cook
2002-03-29 21:52 ` mtopper
2002-04-02 11:07 ` Pablo Alcaraz
2002-04-02 13:11 ` Rene Rebe
2002-04-02 18:59 ` Erik Ljungström
2002-04-02 19:55 ` Rene Rebe
2002-04-02 22:19 ` Mike Fedyk
2002-04-04 6:02 ` Daniel E. Shipton [this message]
2002-03-29 22:57 ` Request for 2.4.20 to be a non-trivial-bugfixes-only Henning P. Schmiedehausen
2002-03-29 10:21 Request for 2.4.20 to be a non-trivial-bugfixes-only version Ruth Ivimey-Cook
2002-03-29 16:00 ` mtopper
2002-03-29 16:27 ` Alan Cox
2002-03-29 18:15 ` mtopper
2002-03-29 18:42 ` Alan Cox
2002-03-29 21:32 ` Ruth Ivimey-Cook
2002-03-29 19:33 ` Rik van Riel
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=1017900173.18439.10.camel@localhost.localdomain \
--to=dshipton@vrac.iastate.edu \
--cc=Ruth.Ivimey-Cook@ivimey.org \
--cc=hahn@physics.mcmaster.ca \
--cc=insight@metalab.unc.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=mtopper@xarch.tu-graz.ac.at \
--cc=pabloa@laotraesquina.com.ar \
--cc=rene.rebe@gmx.net \
/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