From: miquels@traveler.cistron-office.nl (Miquel van Smoorenburg)
To: linux-kernel@vger.kernel.org
Subject: Re: Signal 11
Date: 15 Dec 2000 00:10:24 GMT [thread overview]
Message-ID: <91bnhg$vij$1@enterprise.cistron.net> (raw)
In-Reply-To: <Pine.LNX.4.10.10012141434320.12451-100000@penguin.transmeta.com> <Pine.LNX.4.30.0012142351520.19104-100000@bochum.redhat.de>
In article <Pine.LNX.4.30.0012142351520.19104-100000@bochum.redhat.de>,
Bernhard Rosenkraenzer <bero@redhat.de> wrote:
>The same thing is true of *any* gcc release.
>For example, C++-ABI wise, 2.95.x is incompatible BOTH with egcs 1.1.x
>_and_ the upcoming 3.0 release.
Yes, but 2.96 is also binary incompatible with all non-redhat distro's.
And since redhat is _the_ distro that commercial entities use to
release software for, this was very arguably a bad move.
There's simply no excuse. It's too obvious.
Mike.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-15 0:41 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-14 12:42 Signal 11 Clayton Weaver
2000-12-14 19:11 ` Linus Torvalds
2000-12-14 22:35 ` Alan Cox
2000-12-14 22:45 ` Linus Torvalds
2000-12-14 22:58 ` Bernhard Rosenkraenzer
2000-12-14 23:11 ` Linus Torvalds
2000-12-15 0:10 ` Miquel van Smoorenburg [this message]
2000-12-15 0:32 ` Alan Cox
2000-12-15 0:42 ` Miquel van Smoorenburg
2000-12-15 2:07 ` Michael Peddemors
2000-12-15 1:09 ` Alan Cox
2000-12-15 16:12 ` Theodore Y. Ts'o
2000-12-14 23:24 ` Alan Cox
2000-12-14 23:35 ` Jakub Jelinek
2000-12-14 23:51 ` Linus Torvalds
2000-12-15 0:11 ` Dan Egli
2000-12-16 1:28 ` Signal 11gy Alan Cox
2000-12-14 22:46 ` Signal 11 Jakub Jelinek
-- strict thread matches above, loose matches on Subject: below --
2000-12-09 5:32 davej
2000-12-08 0:27 Linux 2.2.18pre25 Alan Cox
2000-12-08 0:44 ` Signal 11 Rainer Mager
2000-12-08 1:05 ` Jeff V. Merkey
2000-12-08 1:09 ` Michel LESPINASSE
2000-12-08 2:14 ` Rainer Mager
2000-12-08 1:20 ` Andi Kleen
2000-12-08 1:24 ` Jeff V. Merkey
2000-12-08 1:40 ` Andi Kleen
2000-12-08 1:43 ` Jeff V. Merkey
2000-12-08 1:55 ` Jeff V. Merkey
2000-12-08 19:20 ` Dr. Kelsey Hudson
2000-12-08 2:28 ` davej
2000-12-08 3:13 ` Jeff V. Merkey
2000-12-08 3:25 ` davej
2000-12-08 16:44 ` Matthew Vanecek
2000-12-08 19:43 ` Dr. Kelsey Hudson
2000-12-08 13:52 ` Alan Cox
2000-12-15 0:11 ` lamont
2000-12-08 1:58 ` Richard B. Johnson
2000-12-08 2:04 ` Peter Samuelson
2000-12-08 16:36 ` Matthew Vanecek
2000-12-08 16:49 ` Richard B. Johnson
2000-12-08 17:40 ` Peter Samuelson
2000-12-08 19:36 ` Dr. Kelsey Hudson
2000-12-08 9:46 ` David Woodhouse
2000-12-08 14:06 ` Alan Cox
2000-12-09 19:01 ` Matthew Vanecek
2000-12-09 19:20 ` davej
2000-12-09 23:31 ` Matthew Vanecek
2000-12-11 0:58 ` Rainer Mager
2000-12-11 9:05 ` Rainer Mager
2000-12-11 13:33 ` Mike Galbraith
2000-12-11 23:24 ` Rainer Mager
2000-12-11 14:14 ` davej
2000-12-08 16:21 ` Horst von Brand
2000-12-08 19:34 ` Mark Vojkovich
2000-12-08 23:16 ` Jeff V. Merkey
2000-12-08 22:24 ` David Woodhouse
2000-12-09 0:56 ` Jeff V. Merkey
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='91bnhg$vij$1@enterprise.cistron.net' \
--to=miquels@traveler.cistron-office.nl \
--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.