public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Halasa <khc@pm.waw.pl>
To: Adrian Bunk <bunk@stusta.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: RFC: Raise required gcc version to 3.2 ?
Date: Thu, 28 Jul 2005 14:39:12 +0200	[thread overview]
Message-ID: <m3hdefxfyn.fsf@defiant.localdomain> (raw)
In-Reply-To: <20050728120012.GB3528@stusta.de> (Adrian Bunk's message of "Thu, 28 Jul 2005 14:00:12 +0200")

Adrian Bunk <bunk@stusta.de> writes:

> Is there any good reason why we should not drop support for older 
> compilers?

Compilation speed? Don't know, using 3 (4?) years old Athlon 2000
it's not a problem unless I need full build 30 times a day.

But people on 266 MHz ARM5 may notice.
-- 
Krzysztof Halasa

  reply	other threads:[~2005-07-28 12:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-28 12:00 RFC: Raise required gcc version to 3.2 ? Adrian Bunk
2005-07-28 12:39 ` Krzysztof Halasa [this message]
2005-07-28 13:59   ` Lennart Sorensen
2005-07-28 17:05 ` Christoph Lameter
  -- strict thread matches above, loose matches on Subject: below --
2005-07-28 16:48 Mikael Pettersson
2005-07-29 15:56 ` 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=m3hdefxfyn.fsf@defiant.localdomain \
    --to=khc@pm.waw.pl \
    --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