From: Joe <joecool1029@gmail.com>
To: Bill Davidsen <davidsen@tmr.com>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: remove support for gcc < 3.2
Date: Wed, 10 Aug 2005 20:02:33 -0400 [thread overview]
Message-ID: <d4757e6005081017024c3bf3fd@mail.gmail.com> (raw)
In-Reply-To: <42FA5848.809@tmr.com>
I'm for its removal. As for the gcc project "losing its way" consider
that 3.4 has quite matured and also has much smaller binary size from
3.3. 4.0 however is still too early in its development to come close
to surpassing 3.4.
With all the changes and deprications it seems pointless to have to
maintain extra code so 3 people can use an obsolete compiler.
Something more recent like 3.4 should be used as a bench.
Just my two cents.
next prev parent reply other threads:[~2005-08-11 0:02 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-31 22:26 [2.6 patch] remove support for gcc < 3.2 Adrian Bunk
2005-07-31 22:36 ` David S. Miller
2005-07-31 23:08 ` Nigel Cunningham
2005-08-07 16:25 ` Denis Vlasenko
2005-08-10 19:40 ` Bill Davidsen
2005-08-11 0:02 ` Joe [this message]
2005-08-11 0:05 ` David S. Miller
2005-08-13 3:27 ` Bill Davidsen
2005-08-01 3:01 ` [2.6 patch] " Kurt Wall
2005-08-02 5:37 ` Willy Tarreau
2005-08-01 4:27 ` Miles Bader
2005-08-02 21:46 ` Jan-Benedict Glaw
2005-08-03 2:08 ` Gustavo Guillermo Pérez
2005-08-04 0:53 ` Mathieu Chouquet-Stringer
2005-08-04 20:34 ` networking problems when using gcc 4.0.1 Adrian Bunk
2005-08-04 1:34 ` [2.6 patch] remove support for gcc < 3.2 Dave Airlie
2005-08-04 6:54 ` Jan-Benedict Glaw
2005-08-04 20:38 ` Adrian Bunk
2005-08-05 21:14 ` Jan-Benedict Glaw
2005-08-05 21:30 ` Martin Drab
2005-08-05 21:37 ` Jan-Benedict Glaw
2005-08-13 9:21 ` Jan-Benedict Glaw
2005-08-12 7:40 ` Geert Uytterhoeven
2005-08-12 10:40 ` Maciej W. Rozycki
2005-08-12 12:29 ` Jan-Benedict Glaw
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=d4757e6005081017024c3bf3fd@mail.gmail.com \
--to=joecool1029@gmail.com \
--cc=akpm@osdl.org \
--cc=davidsen@tmr.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