From: Daniel Phillips <phillips@bonn-fries.net>
To: Keith Owens <kaos@ocs.com.au>, Paul P Komkoff Jr <i@stingr.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [ANNOUNCE] kbuild 2.5 ports for -pre9 and -pre9-ac1
Date: Mon, 3 Jun 2002 12:12:10 +0200 [thread overview]
Message-ID: <E17Eoot-0000sG-00@starship> (raw)
In-Reply-To: <31456.1023084181@kao2.melbourne.sgi.com>
On Monday 03 June 2002 08:03, Keith Owens wrote:
> On Thu, 30 May 2002 23:55:44 +0400,
> Paul P Komkoff Jr <i@stingr.net> wrote:
> >I'm here to announce updates of kbuild 2.5 patch to apply on 2.4.19-pre9 and
> >2.4.19-pre9-ac1
>
> Thanks for this, it shows that other people can do kbuild 2.5 work.
>
> However there are no plans to replace the kernel build method in 2.4
> kernels, it is too big a change for a stable kernel. I have already
> extracted several bugs fixes from kbuild 2.5 and fed them to Marcelo or
> Alan Cox.
However, for folks like me who develop mainly on the 2.4 kernel this
is a real blessing, and I hope Paul continues to maintain this.
> There is a limited amount that can be fixed in the 2.4 kernel build
> without a large impact on users. Anything that forces an upgrade past
> make 3.77.1 (the currently required version on 2.4 kernels) is
> unacceptable.
<checks make version>
Oh, I've got 3.79.1, there ya go, I guess that's why it works. Thanks
once again, debian gnomes. Anyway, there's not a lot to fear since
the patch has no apparent ill effect on the operation of old kbuild.
I'm not advocating that Marcelo merge it just yet, no rush. It
obviously needs to mature in 2.5 first.
--
Daniel
prev parent reply other threads:[~2002-06-03 10:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-30 19:55 [ANNOUNCE] kbuild 2.5 ports for -pre9 and -pre9-ac1 Paul P Komkoff Jr
2002-06-03 6:03 ` Keith Owens
2002-06-03 10:12 ` Daniel Phillips [this message]
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=E17Eoot-0000sG-00@starship \
--to=phillips@bonn-fries.net \
--cc=i@stingr.net \
--cc=kaos@ocs.com.au \
--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