From: hpa@zytor.com (H. Peter Anvin)
To: linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] add compiler-gcc4.h
Date: Thu, 3 Feb 2005 01:04:46 +0000 (UTC) [thread overview]
Message-ID: <ctrtbe$570$1@terminus.zytor.com> (raw)
In-Reply-To: 41FCFED4.1070301@tiscali.de
Followup to: <41FCFED4.1070301@tiscali.de>
By author: Matthias-Christian Ott <matthias.christian@tiscali.de>
In newsgroup: linux.dev.kernel
>
> Hi!
> But maybe gcc 4 will get different later, so I think this patch makes sense.
>
No, it doesn't. You fork when you have a reason. Eager forking is
*BAD*.
-hpa
next prev parent reply other threads:[~2005-02-03 1:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-30 13:03 [2.6 patch] add compiler-gcc4.h Adrian Bunk
2005-01-30 14:11 ` Andi Kleen
2005-01-30 14:14 ` Adrian Bunk
2005-01-30 15:35 ` Matthias-Christian Ott
2005-02-03 1:04 ` H. Peter Anvin [this message]
2005-02-05 13:50 ` Adrian Bunk
2005-02-05 18:45 ` H. Peter Anvin
2005-02-05 19:38 ` Adrian Bunk
2005-02-05 19:52 ` H. Peter Anvin
2005-02-06 0:43 ` [RFC][PATCH-2.6] Clean up and merge compiler-*.h Kyle Moffett
2005-02-06 0:50 ` [2.6 patch] add compiler-gcc4.h Adrian Bunk
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='ctrtbe$570$1@terminus.zytor.com' \
--to=hpa@zytor.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox