From: Daniel Phillips <phillips@bonn-fries.net>
To: Keith Owens <kaos@ocs.com.au>, kbuild-devel@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: Announce: Kernel Build for 2.5, Release 2.1 is available
Date: Sun, 21 Apr 2002 16:32:35 +0200 [thread overview]
Message-ID: <E16zIOJ-0001Fh-00@starship> (raw)
In-Reply-To: <27268.1019374988@ocs3.intra.ocs.com.au>
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.
Hi Keith,
Have you got an update on first-time build performance? Not that I'm all
that worried about it, incremental performance is *way* more important to
me, however, first-time performance seems to be something of a predictor
of when your work will get into mainline.
I'm marking each day that kbuild 2.5 isn't in mainline on the wall of my
little cave here, as every day kbuild 2.bad.old continues find some way of
wasting my time.
By the way, is there a reason for not providing a single bzip of all the
2.4 + 2.5 files? Not that the slight inconvenience matters all that much,
since hopefully it will all be in mainline soon.
Downloaded, installing...
--
Daniel
next prev parent reply other threads:[~2002-04-22 14:32 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 [this message]
2002-04-22 23:00 ` Keith Owens
2002-04-21 23:04 ` Daniel Phillips
2002-04-22 23:54 ` Keith Owens
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=E16zIOJ-0001Fh-00@starship \
--to=phillips@bonn-fries.net \
--cc=kaos@ocs.com.au \
--cc=kbuild-devel@lists.sourceforge.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