public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: kbuild-devel@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org
Subject: Announce: Kernel Build for 2.5, release 3.0 is available
Date: Mon, 03 Jun 2002 12:35:05 +1000	[thread overview]
Message-ID: <27953.1023071705@kao2.melbourne.sgi.com> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Content-Type: text/plain; charset=us-ascii

Release 3.0 of kernel build for kernel 2.5 (kbuild 2.5) is available.
http://sourceforge.net/projects/kbuild/, package kbuild-2.5, download
release 3.0.

kbuild-2.5-core-15
  Changes from core-14.

    Replace mdbm with kbuild specific database engine to increase
    performance.

    Remove CML2 support, Dominik Brodowski, Keith Owens.

    Remove the restriction on symlinked sources and targets.  Aegis
    users should be able to use kbuild 2.5 now.

kbuild-2.5-common-2.5.19-1.
  Changes from common-2.5.15-4.

    Upgrade to kernel 2.5.19.
   
kbuild-2.5-i386-2.5.19-1.
  Changes from i386-2.5.15-2.

    Upgrade to kernel 2.5.19.


Larry McVoy provided the mdbm database engine from BitKeeper for use in
kbuild 2.5 release 2.0-2.4, and was extremely helpful in answering my
questions about mdbm.  Unfortunately some of the processing required by
kbuild 2.5 did not fit well with the mdbm model.  Since an application
specific database will always outperform a generic database, I took
advantage of knowledge about the kbuild data and wrote an application
specific database engine.

This is not a criticism of mdbm - it is a good generic database engine.
I could squeeze a few more seconds out of the build time by using
application specific knowledge.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: Exmh version 2.1.1 10/15/1999

iD8DBQE8+tXYi4UHNye0ZOoRAp+5AJ9evi07/7D1+xHRRnxA8xdpeqY3hgCeMcrH
kgNAIKaGHE1Fy8BKByBZqXs=
=EamL
-----END PGP SIGNATURE-----


             reply	other threads:[~2002-06-03  2:35 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-03  2:35 Keith Owens [this message]
2002-06-03  5:31 ` Announce: Kernel Build for 2.5, release 3.0 is available Keith Owens
2002-06-03 19:22 ` [kbuild-devel] " Thomas Duffy
2002-06-03 19:31   ` Thunder from the hill
2002-06-03 19:58     ` Thomas Duffy
2002-06-03 20:06       ` Thunder from the hill
2002-06-03 21:12         ` Thomas Duffy
2002-06-04  0:19   ` Keith Owens
2002-06-04  0:29     ` Thomas Duffy
2002-06-04  4:53 ` Keith Owens
2002-06-04  9:16   ` Alex Riesen
2002-06-04 22:55     ` Keith Owens
2002-06-05  2:25       ` [kbuild-devel] " John Cowan
2002-06-05  2:38         ` Keith Owens
2002-06-05 18:13         ` Mark Mielke
2002-06-05 13:19       ` Alex Riesen
2002-06-04 13:59   ` [kbuild-devel] " Arnd Bergmann
2002-06-05 13:53   ` Keith Owens
2002-06-07  8:49     ` Keith Owens
2002-06-12 13:54       ` Keith Owens
2002-06-12 20:55         ` [kbuild-devel] " Thomas Duffy
2002-06-13  0:15           ` Keith Owens
  -- strict thread matches above, loose matches on Subject: below --
2002-06-03  4:06 Hayden James
2002-06-03  4:14 ` Keith Owens
2002-06-03  4:51 ` Thunder from the hill

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=27953.1023071705@kao2.melbourne.sgi.com \
    --to=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