public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Willy Tarreau <w@1wt.eu>
Cc: Mikael Pettersson <mikpe@csd.uu.se>,
	Andreas Steinmetz <ast@domdv.de>,
	Arjan van de Ven <arjan@infradead.org>,
	linux-kernel@vger.kernel.org, mtosatti@redhat.com
Subject: Re: Linux 2.4.34-pre1
Date: Mon, 21 Aug 2006 02:56:08 +0200	[thread overview]
Message-ID: <20060821005608.GD11651@stusta.de> (raw)
In-Reply-To: <20060817204307.GA17391@1wt.eu>

On Thu, Aug 17, 2006 at 10:43:07PM +0200, Willy Tarreau wrote:

> Hi Adrian,

Hi Willy,

>...
> Basically, my goal is to keep all those users trusting Linux (other
> systems such as OpenBSD are very present in this area too). And your
> goal is to progressively attract them towards 2.6 with strong arguments
> in favor of 2.6 (and not against 2.4) that only them will judge relevant
> based on their usage. And I can tell you that 2.4 being harder to build
> than 2.6 is obviously not a relevant argument in favor of 2.6 for people
> who apply more than 100 patches to their kernels.

it was not my goal to make it harder for people to build 2.4.

I'd in fact consider userspace and hardware support the real problems 
for people who want to use kernel 2.4 - using a different compiler is
a relatively easy issue compared to this.

And I had mixed two complete different points in this thread:
- untested kernel 2.4 / gcc 4
- kernel 2.6 shouldn't be in any respect worse than kernel 2.4

Looking at the kenrel size, it seems the latter is far from being true 
in this respect.  :-(

The "untested" still applies.
But I do also understand your points regardingthis issue.

If I was 2.4 maintainer, I wouldn't apply the patch to allow gcc 4.
But you are the 2.4 maintainer, and it's therefore your decision.

> Best regards,
> Willy

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


  parent reply	other threads:[~2006-08-21  0:56 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-16 22:36 Linux 2.4.34-pre1 Willy Tarreau
2006-08-16 23:54 ` Adrian Bunk
2006-08-17  5:16   ` Willy Tarreau
2006-08-17  6:48     ` Arjan van de Ven
2006-08-17  8:35       ` Andreas Steinmetz
2006-08-17  8:50         ` Mikael Pettersson
2006-08-17 12:48           ` Adrian Bunk
2006-08-17 20:43             ` Willy Tarreau
2006-08-17 23:41               ` Gerd v. Egidy
2006-08-18  4:40                 ` Willy Tarreau
2006-08-21  0:56               ` Adrian Bunk [this message]
2006-08-17  9:06         ` Adrian Bunk
2006-08-17  9:16           ` Andreas Steinmetz
2006-08-18 23:25             ` Adrian Bunk
2006-08-19  1:20               ` Grant Coady
2006-08-20 17:27                 ` Adrian Bunk
2006-08-19  4:45               ` Willy Tarreau
2006-08-21  0:35                 ` Adrian Bunk
2006-08-21  0:41                   ` Willy Tarreau
2006-08-21  1:07                     ` Adrian Bunk
2006-08-17  8:37       ` Willy Tarreau
2006-08-17  9:12 ` Thomas Voegtle
2006-08-18 22:48 ` Solar Designer
2006-08-18 23:11   ` Adrian Bunk
2006-08-18 23:27     ` Solar Designer
  -- strict thread matches above, loose matches on Subject: below --
2006-08-17  7:57 Chris Rankin
2006-08-17  9:16 ` Thomas Backlund
2006-08-18  4:47   ` Willy Tarreau

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=20060821005608.GD11651@stusta.de \
    --to=bunk@stusta.de \
    --cc=arjan@infradead.org \
    --cc=ast@domdv.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikpe@csd.uu.se \
    --cc=mtosatti@redhat.com \
    --cc=w@1wt.eu \
    /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