From: Mike Fedyk <mfedyk@matchmail.com>
To: John Stoffel <stoffel@casc.com>
Cc: DevilKin <DevilKin-LKML@blindguardian.org>,
Marcelo Tosatti <marcelo@conectiva.com.br>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.4.18
Date: Mon, 25 Feb 2002 13:54:52 -0800 [thread overview]
Message-ID: <20020225215452.GB27211@matchmail.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0202251613300.31438-100000@freak.distro.conectiva> <20020225203750.C531B218392@tartarus.telenet-ops.be> <15482.44226.126189.431079@gargle.gargle.HOWL>
In-Reply-To: <15482.44226.126189.431079@gargle.gargle.HOWL>
On Mon, Feb 25, 2002 at 04:29:38PM -0500, John Stoffel wrote:
>
> DevilKin> Wouldn't it be easier just to make a new 2.4.18 with the
> DevilKin> patch applied?
>
> Or just release 2.4.19 right away with the patch applied and start all
> over again on 2.4.20-pre1 instead?
>
You have got to be kidding me.
The only binaries that are affected are ones compiles without shared
libraries on some non-x86 arches, and anyone doing that should know what
they are doing and which kernels to use.
Does anyone know how long this bug has been in the kernel?
Mike
next prev parent reply other threads:[~2002-02-25 21:55 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-25 20:20 Linux 2.4.18 Holzrichter, Bruce
2002-02-25 19:18 ` Marcelo Tosatti
2002-02-24 5:08 ` Daniel Phillips
2002-02-25 20:37 ` DevilKin
2002-02-25 20:45 ` Thomas Glanzmann
2002-02-25 21:29 ` John Stoffel
2002-02-25 21:54 ` Mike Fedyk [this message]
2002-02-25 21:57 ` John Stoffel
2002-02-25 22:05 ` David S. Miller
2002-02-25 22:58 ` Bernd Eckenfels
2002-02-26 0:19 ` Harald Arnesen
2002-02-25 22:56 ` Bernd Eckenfels
2002-02-26 0:22 ` Harald Arnesen
2002-02-26 0:28 ` Eric Krout
2002-02-26 3:06 ` Andreas Dilger
2002-02-26 16:46 ` Stephan von Krawczynski
2002-02-26 17:13 ` Rik van Riel
2002-02-26 17:50 ` Stephan von Krawczynski
2002-02-26 19:42 ` Felix Seeger
2002-02-28 22:25 ` Bill Davidsen
2002-02-25 20:27 ` Christoph Hellwig
[not found] <20020225200618.0FAE82069E@eos.telenet-ops.be>
2002-02-25 19:31 ` Marcelo Tosatti
2002-02-24 5:20 ` Daniel Phillips
2002-02-24 5:28 ` Daniel Phillips
2002-02-25 22:08 ` David S. Miller
2002-02-25 22:14 ` Thomas Duffy
2002-02-25 22:16 ` David S. Miller
2002-02-25 22:28 ` Lars Marowsky-Bree
2002-02-25 22:20 ` Rainer Ellinger
2002-02-25 22:19 ` David S. Miller
2002-02-25 23:01 ` Matthias Andree
2002-02-25 23:08 ` David S. Miller
2002-02-25 23:21 ` Jan Niehusmann
2002-02-25 23:32 ` Matthias Andree
2002-02-26 5:04 ` Bill Davidsen
2002-02-26 5:18 ` H. Peter Anvin
2002-02-26 9:09 ` Matthias Andree
2002-02-25 23:34 ` H. Peter Anvin
2002-02-25 23:55 ` David S. Miller
2002-02-26 1:09 ` David Relson
2002-02-26 13:25 ` Juan Quintela
2002-02-25 22:25 ` H. Peter Anvin
2002-02-25 22:50 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2002-02-25 18:37 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 20:09 ` 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=20020225215452.GB27211@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=DevilKin-LKML@blindguardian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=stoffel@casc.com \
/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