From: Adrian Bunk <bunk@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andi Kleen <ak@suse.de>, Randy Dunlap <randy.dunlap@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>,
Jarek Poplawski <jarkao2@o2.pl>,
linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org
Subject: Re: RFC: drop support for gcc < 4.0
Date: Tue, 21 Aug 2007 22:21:13 +0200 [thread overview]
Message-ID: <20070821202113.GF30705@stusta.de> (raw)
In-Reply-To: <alpine.LFD.0.999.0708211306560.30176@woody.linux-foundation.org>
On Tue, Aug 21, 2007 at 01:08:25PM -0700, Linus Torvalds wrote:
>
>
> On Tue, 21 Aug 2007, Adrian Bunk wrote:
> > >
> > > Bogus warnings should be relatively harmless.
> >
> > How many kernel developers use such old gcc versions?
>
> It's NOT about "kernel developers".
>
> It's about random people testing kernels.
>
> If we make it harder for people to test kernels, we're going to lose. So
> no, I vote for *not* cutting off old gcc versions unless it's absolutely
> fatal.
How many people e.g. test -rc kernels compiled with gcc 3.2?
> Linus
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2007-08-21 20:22 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-21 13:20 2.6.23-rc3-git3 make warnings Jarek Poplawski
2007-08-21 15:07 ` [Git Patch] ACPI: Fix a warning of discarding qualifiers from pointer target type WANG Cong
2007-08-21 15:14 ` Alexey Starikovskiy
2007-08-21 15:18 ` Al Viro
2007-08-21 15:22 ` Alexey Starikovskiy
2007-08-21 15:47 ` Al Viro
2007-08-23 0:59 ` Brown, Len
2007-08-23 1:28 ` Al Viro
2007-08-22 7:57 ` Jarek Poplawski
2007-08-21 16:17 ` 2.6.23-rc3-git3 make warnings WANG Cong
2007-08-21 16:44 ` Greg KH
2007-08-21 16:57 ` Adrian Bunk
2007-08-21 16:31 ` Randy Dunlap
2007-08-21 17:35 ` RFC: drop support for gcc < 4.0 Adrian Bunk
2007-08-21 17:54 ` Russell King
2007-08-21 18:14 ` Kyle McMartin
2007-08-21 18:29 ` Adrian Bunk
2007-08-22 5:48 ` Robert P. J. Day
2007-08-21 18:25 ` Chris Wedgwood
2007-08-21 20:41 ` Glauber de Oliveira Costa
2007-08-21 20:56 ` Segher Boessenkool
2007-08-21 21:01 ` Glauber de Oliveira Costa
2007-08-22 6:59 ` Thomas Bogendoerfer
2007-08-22 18:15 ` Ralf Baechle
2007-08-21 19:19 ` Andi Kleen
2007-08-21 19:54 ` Adrian Bunk
2007-08-21 20:07 ` [RFC][PATCH] introduce TASK_SIZE_OF() for all arches Matthew Wilcox
2007-08-21 20:08 ` RFC: drop support for gcc < 4.0 Linus Torvalds
2007-08-21 20:21 ` Adrian Bunk [this message]
2007-08-21 20:32 ` Linus Torvalds
2007-08-22 7:36 ` Jarek Poplawski
2007-08-21 20:49 ` Segher Boessenkool
2007-08-21 21:21 ` Adrian Bunk
2007-08-21 21:49 ` James Bottomley
2007-08-21 22:09 ` Adrian Bunk
2007-08-22 0:08 ` Segher Boessenkool
2007-08-22 6:07 ` Jarek Poplawski
2007-08-21 21:41 ` Oliver Pinter
2007-08-22 7:57 ` Jan Engelhardt
2007-08-22 8:08 ` Jarek Poplawski
2007-08-22 8:10 ` Jan Engelhardt
2007-08-22 8:42 ` Michal Piotrowski
2007-08-22 8:56 ` Jarek Poplawski
2007-08-22 8:48 ` Martin Michlmayr
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=20070821202113.GF30705@stusta.de \
--to=bunk@kernel.org \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=jarkao2@o2.pl \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=torvalds@linux-foundation.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