From: Daniel.Egger@t-online.de (Daniel Egger)
To: egcs@cygnus.com
Cc: linux kernel <linux-kernel@vger.rutgers.edu>
Subject: Re: linux and EGCS PATCH
Date: Thu, 11 Dec 1997 16:33:00 -0000 [thread overview]
Message-ID: <97121118012601.00692@server.paf.main> (raw)
On Wed, 10 Dec 1997, you wrote:
>So at this point, I haven't had any real indications of the kernel doing
>anything wrong, and egcs should be considered broken for now. I can be
>made to change my mind, but so far all the indications are that if you
>want a stable kernel you should not use egcs yet.
Hm, here works a linux kernel version 2.1.72 compiled with egcs-971207 on i486.
It's up now for 48h and stands heavy network traffic without any problems.
Servus,
Daniel
next reply other threads:[~1997-12-11 16:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-12-11 16:33 Daniel Egger [this message]
1997-12-12 10:18 ` linux kernel account
-- strict thread matches above, loose matches on Subject: below --
1997-12-05 1:17 Martin.Dalecki
1997-12-05 10:44 ` Linus Torvalds
1997-12-06 8:41 ` Jeffrey A Law
1997-12-10 8:57 ` Horst von Brand
1997-12-10 10:58 ` Paul Koning
1997-12-10 10:58 ` Linus Torvalds
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=97121118012601.00692@server.paf.main \
--to=daniel.egger@t-online.de \
--cc=egcs@cygnus.com \
--cc=linux-kernel@vger.rutgers.edu \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).