From: vda <vda@port.imtp.ilyichevsk.odessa.ua>
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 1.5 is available
Date: Tue, 6 Nov 2001 14:46:09 +0000 [thread overview]
Message-ID: <01110614460902.00798@nemo> (raw)
In-Reply-To: <20208.1005048011@ocs3.intra.ocs.com.au>
In-Reply-To: <20208.1005048011@ocs3.intra.ocs.com.au>
On Tuesday 06 November 2001 12:00, Keith Owens wrote:
> Release 1.5 of kernel build for kernel 2.5 (kbuild 2.5) has been
> released. http://sourceforge.net/projects/kbuild/, Package kbuild-2.5,
> download release 1.5.
>
> http://marc.theaimsgroup.com/?l=linux-kernel&m=99725412902968&w=2
> contains information about the base release.
I don't use kbuild yet but really like the idea.
What prevents its adoption as a standard kernel build tool?
--
vda
next prev parent reply other threads:[~2001-11-06 12:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-06 12:00 Announce: Kernel Build for 2.5, Release 1.5 is available Keith Owens
2001-11-06 14:46 ` vda [this message]
2001-11-06 14:56 ` Keith Owens
2001-11-06 15:41 ` Dave Jones
2001-11-06 23:11 ` Keith Owens
2001-11-06 17:39 ` Peter Samuelson
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=01110614460902.00798@nemo \
--to=vda@port.imtp.ilyichevsk.odessa.ua \
--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