From: John Levon <levon@movementarian.org>
To: Andi Kleen <ak@suse.de>
Cc: Jeff Garzik <jgarzik@pobox.com>, linux-kernel@vger.kernel.org
Subject: Re: [AMD64 1/3] fix C99-style declarations
Date: Sat, 25 Oct 2003 22:03:14 +0100 [thread overview]
Message-ID: <20031025210313.GA79137@compsoc.man.ac.uk> (raw)
In-Reply-To: <20031025205617.GD27754@wotan.suse.de>
On Sat, Oct 25, 2003 at 10:56:17PM +0200, Andi Kleen wrote:
> I don't think it makes much difference. People hacking on one architecture
> break other architectures all the time for various reasons, e.g.
> the implicit includes in different architectures vary widely.
An unusual argument ...
> The few people left who use 2.95 will just have to live with
I am a little dubious it's "few people". (especially as gcc 2.96 has the
same problem).
regards,
john
--
Khendon's Law:
If the same point is made twice by the same person, the thread is over.
next prev parent reply other threads:[~2003-10-25 21:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-25 18:28 [AMD64 1/3] fix C99-style declarations Jeff Garzik
2003-10-25 20:27 ` Andi Kleen
2003-10-25 20:47 ` John Levon
2003-10-25 20:56 ` Andi Kleen
2003-10-25 21:03 ` John Levon [this message]
2003-10-28 9:20 ` Pavel Machek
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=20031025210313.GA79137@compsoc.man.ac.uk \
--to=levon@movementarian.org \
--cc=ak@suse.de \
--cc=jgarzik@pobox.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