From: "H. Peter Anvin" <hpa@zytor.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] add compiler-gcc4.h
Date: Sat, 05 Feb 2005 10:45:52 -0800 [thread overview]
Message-ID: <42051460.9060208@zytor.com> (raw)
In-Reply-To: <20050205135026.GC3129@stusta.de>
Adrian Bunk wrote:
>
> As I already said in this thread:
> The currently used file for gcc 4 is compiler-gcc+.h, not
> compiler-gcc3.h .
>
> And the current setup is to have one file for every major number of gcc.
> I have no strong opinion whether this approach or the approach of one
> file for all gcc versions is better - but with the current approach,
> everything else than a separate file for gcc 4 wasn't logical.
Yes it is. It's perfectly logical: gcc+ contains the "going forward"
version, and until it supports some feature that isn't in all versions
of gcc4, it's the right thing to do.
> I can offer the following choices:
> - please apply this compiler-gcc4.h patch
> - let me send a patch merging all compiler-gcc*.h files into one
> compiler-gcc.h file
> - let me send a patch merging all compiler-gcc*.h files back into
> compiler.h
No. Leave it the way it currently is until there is a *reason* to fork
a gcc4 module.
This isn't a cleanup you're proposing, it's a mess-up.
-hpa
next prev parent reply other threads:[~2005-02-05 18:50 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
2005-02-05 13:50 ` Adrian Bunk
2005-02-05 18:45 ` H. Peter Anvin [this message]
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=42051460.9060208@zytor.com \
--to=hpa@zytor.com \
--cc=akpm@osdl.org \
--cc=bunk@stusta.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox