From: Nigel Cunningham <ncunningham@cyclades.com>
To: "David S. Miller" <davem@davemloft.net>
Cc: bunk@stusta.de, Andrew Morton <akpm@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [2.6 patch] remove support for gcc < 3.2
Date: Mon, 01 Aug 2005 09:08:19 +1000 [thread overview]
Message-ID: <1122851299.4351.278.camel@localhost> (raw)
In-Reply-To: <20050731.153631.70217457.davem@davemloft.net>
Hi.
On Mon, 2005-08-01 at 08:36, David S. Miller wrote:
> Many people still use 2.95 because it's still the fastest
> way to get a kernel build done and that's important for
> many people.
Yes, please don't remove 2.95 support.
Regards,
Nigel
--
Evolution.
Enumerate the requirements.
Consider the interdependencies.
Calculate the probabilities.
next prev parent reply other threads:[~2005-07-31 23:09 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 [this message]
2005-08-07 16:25 ` Denis Vlasenko
2005-08-10 19:40 ` Bill Davidsen
2005-08-11 0:02 ` Joe
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=1122851299.4351.278.camel@localhost \
--to=ncunningham@cyclades.com \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=davem@davemloft.net \
--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