From: Keith Owens <kaos@ocs.com.au>
To: Daniel Phillips <phillips@bonn-fries.net>
Cc: kbuild-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: Announce: Kernel Build for 2.5, Release 2.1 is available
Date: Tue, 23 Apr 2002 09:54:12 +1000 [thread overview]
Message-ID: <6557.1019519652@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "Mon, 22 Apr 2002 01:04:12 +0200." <E16zQNR-0001NS-00@starship>
On Mon, 22 Apr 2002 01:04:12 +0200,
Daniel Phillips <phillips@bonn-fries.net> wrote:
>On Tuesday 23 April 2002 01:00, Keith Owens wrote:
>> On Sun, 21 Apr 2002 16:32:35 +0200,
>> Daniel Phillips <phillips@bonn-fries.net> wrote:
>> >On Sunday 21 April 2002 09:43, Keith Owens wrote:
>> >> Content-Type: text/plain; charset=us-ascii
>> >>
>> >> Release 2.1 of kernel build for kernel 2.5 (kbuild 2.5) is available.
>> >> http://sourceforge.net/projects/kbuild/, Package kbuild-2.5, download
>> >> release 2.1.
>> >
>> >Have you got an update on first-time build performance?
>>
>> 30% faster than the existing kernel build system.
>
>Egad. And we're waiting for what, exactly?
For me to be satisfied that the code is stable, the rewrite with go
faster stripes is less than four weeks old.
For more arch maintainers to convert 2.5.8/arch/$(ARCH) to kbuild 2.5.
i386 is converted, I am working on ia64, Tom Duffy is working on
sparc64, Greg Banks is working on superh. I would like patches for
ppc, s390, alpha etc. as well but will go without them if necessary,
they can catch up later.
Then I will contact Linus.
next prev parent reply other threads:[~2002-04-22 23:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-21 7:43 Announce: Kernel Build for 2.5, Release 2.1 is available Keith Owens
2002-04-21 13:53 ` Keith Owens
2002-04-21 14:32 ` Daniel Phillips
2002-04-22 23:00 ` Keith Owens
2002-04-21 23:04 ` Daniel Phillips
2002-04-22 23:54 ` Keith Owens [this message]
2002-04-22 23:57 ` Keith Owens
2002-04-22 14:36 ` Alex Riesen
2002-04-22 23:03 ` Keith Owens
2002-04-23 9:23 ` Alex Riesen
2002-04-23 22:29 ` Keith Owens
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=6557.1019519652@ocs3.intra.ocs.com.au \
--to=kaos@ocs.com.au \
--cc=kbuild-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=phillips@bonn-fries.net \
/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