mirror of https://lore.kernel.org/lkml/
 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 2.2 is available
Date: Fri, 26 Apr 2002 14:42:28 +1000	[thread overview]
Message-ID: <10571.1019796148@kao2.melbourne.sgi.com> (raw)

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

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

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

   kbuild-2.5-core-7.bz2

   kbuild-2.5-common-2.4.18-6.bz2
   kbuild-2.5-i386-2.4.18-2.bz2
   kbuild-2.5-sparc64-2.4.18-2.bz2

   kbuild-2.5-common-2.5.10-1.bz2
   kbuild-2.5-i386-2.5.10-1.bz2

Changes from core-6 to core-7.

   Use cp -f/mv -f in case target files are marked read only.

   Fix bug where a key could be read from a record that had moved.

   Fix bug in handling of absolute link_subdirs().

   Unlink obsolete dependencies correctly.

   Reinstate checks for changed commands in user_command().

Changes from common-2.4.18-5 to common-2.4.18-6.

   Add tftpboot.img.

   Update 53c700 generated script.

   Add -traditional to scsi script pre-processing (unbalanced ' in comments).

Thanks to Tom Duffy for testing above and beyond the call of duty and
for the sparc64 patch.

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

iD8DBQE8yNqyi4UHNye0ZOoRAlZVAKC4kEnB/bYlOQrrjZsJFYQdTMKT0ACffoXB
x2BOQgfM1BPsWqqhZ980pfo=
=AIFS
-----END PGP SIGNATURE-----


             reply	other threads:[~2002-04-26  4:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-26  4:42 Keith Owens [this message]
2002-04-26 16:31 ` Sebastian Droege
2002-04-27  8:45 ` 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=10571.1019796148@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

all inboxes | Powered by JetHome®