From: Rainer Ellinger <rainer@ellinger.de>
To: Justin Piszcz <war@starband.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.18 - Don't get mad...
Date: Mon, 25 Feb 2002 22:53:11 +0100 [thread overview]
Message-ID: <3C7AB247.80307@ellinger.de> (raw)
In-Reply-To: <Pine.LNX.4.21.0202251537080.31438-100000@freak.distro.conectiva> <Pine.LNX.4.21.0202251556140.31438-100000@freak.distro.conectiva> <6ypu2twaz3.fsf@sodium.transmeta.com> <3C7AA8F1.3F93EFB4@starband.net> <20020225222043.B27081@suse.de> <3C7AAD9A.E8A5F93D@starband.net>
Justin Piszcz wrote:
> http://installkernel.com/kernel/index.html
> I hope I got the story right, and I hope this clears things up on 2.4.18.
That might be the most serious bug in this release: people and media reporting a "release problem".
How many people really need that small fix and are not able to take -rc4 instead final? Compared to 2.4.17, there are more than
100 fixes in this release, that could have been more dangerous than this missing function. And there might be still people out
there using 2.4.17 ;-)
--
rainer@ellinger.de
next prev parent reply other threads:[~2002-02-25 21:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-25 18:37 Linux 2.4.18 Marcelo Tosatti
2002-02-25 18:57 ` Marcelo Tosatti
2002-02-25 20:41 ` Daniel Quinlan
2002-02-25 19:40 ` Marcelo Tosatti
2002-02-25 21:13 ` Linux 2.4.18 - Fixed? Justin Piszcz
2002-02-25 21:20 ` Dave Jones
2002-02-25 21:33 ` Linux 2.4.18 - Summary of what happened/how to fix Justin Piszcz
2002-02-25 21:53 ` Rainer Ellinger [this message]
2002-02-25 20:09 ` Linux 2.4.18 Hugh Dickins
2002-02-25 19:03 ` Marcelo Tosatti
2002-02-25 21:45 ` Florian Weimer
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=3C7AB247.80307@ellinger.de \
--to=rainer@ellinger.de \
--cc=linux-kernel@vger.kernel.org \
--cc=war@starband.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