From: "J . A . Magallon" <jamagallon@able.es>
To: "Dieter Nützel" <Dieter.Nuetzel@hamburg.de>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linux Kernel List <linux-kernel@vger.kernel.org>,
Andrea Arcangeli <andrea@suse.de>,
feedback@suse.de
Subject: Re: Linux 2.4.3-ac12
Date: Sun, 22 Apr 2001 21:53:36 +0200 [thread overview]
Message-ID: <20010422215336.A2240@werewolf.able.es> (raw)
In-Reply-To: <01042219261100.01104@SunWave1>
In-Reply-To: <01042219261100.01104@SunWave1>; from Dieter.Nuetzel@hamburg.de on Sun, Apr 22, 2001 at 19:26:11 +0200
On 04.22 Dieter Nützel wrote:
> > My belief however is that several million people have gcc 2.96-69+, about 50
> > are likely to have random cvs snapshots and none of them are going to build
> > kernels with them anyway, as they wont work __builtin_expect or otherwise.
> >
> > Alan
>
> I will not add fuel to the fire, but isn't 2.4.XX the "stable" version?
> And I think most people (here in Europe :-) are running 2.95.2 at the moment.
> But, yes the previously patches fixed it.
>
That's going to change in a few weeks, I suspect. Dunno about SuSE, but just
released Mandrake 8.0 and RedHat 7.1 ship gcc-2.96.
--
J.A. Magallon # Let the source
mailto:jamagallon@able.es # be with you, Luke...
Linux werewolf 2.4.3-ac12 #1 SMP Sun Apr 22 10:27:22 CEST 2001 i686
next prev parent reply other threads:[~2001-04-22 19:54 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-22 17:26 Linux 2.4.3-ac12 Dieter Nützel
2001-04-22 19:53 ` J . A . Magallon [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-04-22 13:48 f5ibh
2001-04-22 14:03 ` Jesper Juhl
2001-04-22 2:53 Alan Cox
2001-04-22 4:17 ` Manuel McLure
2001-04-22 5:47 ` junio
2001-04-22 6:07 ` junio
2001-04-22 10:42 ` Philip Blundell
2001-04-22 12:26 ` Alan Cox
2001-04-22 12:43 ` Philip Blundell
2001-04-22 12:54 ` Alan Cox
2001-04-22 13:00 ` Philip Blundell
2001-04-22 13:10 ` Alan Cox
2001-04-22 13:22 ` Russell King
2001-04-22 13:29 ` Alan Cox
2001-04-22 16:12 ` Jes Sorensen
2001-04-22 16:30 ` Mohammad A. Haque
2001-04-22 17:27 ` Roman Zippel
2001-04-22 17:43 ` Jes Sorensen
2001-04-22 18:42 ` Alan Cox
2001-04-23 6:54 ` Geert Uytterhoeven
2001-04-22 13:51 ` Philip Blundell
2001-04-22 12:11 ` Alan Cox
2001-04-22 12:18 ` Russell King
2001-04-22 12:51 ` Alan Cox
2001-04-22 12:55 ` John Jasen
2001-04-22 13:00 ` Alan Cox
2001-04-22 8:57 ` Eyal Lebedinsky
2001-04-22 12:20 ` Alan Cox
2001-04-22 13:04 ` Eyal Lebedinsky
2001-04-22 16:25 ` John Cavan
2001-04-22 17:07 ` Manuel McLure
2001-04-22 18:48 ` Alan Cox
2001-04-22 18:57 ` Manuel McLure
2001-04-23 0:19 ` John Cavan
2001-04-23 8:35 ` Byeong-ryeol Kim
2001-04-23 22:18 ` Byeong-ryeol Kim
2001-04-22 22:46 ` Mr. James W. Laferriere
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=20010422215336.A2240@werewolf.able.es \
--to=jamagallon@able.es \
--cc=Dieter.Nuetzel@hamburg.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andrea@suse.de \
--cc=feedback@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.