From: Keith Owens <kaos@sgi.com>
To: kdb@oss.sgi.com
Cc: linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org
Subject: Announce: kdb v4.4 is available for kernel 2.6.7
Date: Thu, 17 Jun 2004 11:16:55 +1000 [thread overview]
Message-ID: <3469.1087435015@kao2.melbourne.sgi.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
KDB (Linux Kernel Debugger) has been updated.
ftp://oss.sgi.com/projects/kdb/download/v4.4/
Current versions are :-
kdb-v4.4-2.6.7-common-1.bz2
kdb-v4.4-2.6.7-i386-1.bz2
kdb-v4.4-2.6.7-ia64-1.bz2
Changelog extract since kdb-v4.4-2.6.7-rc2-common-1.
2004-06-16 Keith Owens <kaos@sgi.com>
* kdb v4.4-2.6.7-common-1.
2004-06-09 Keith Owens <kaos@sgi.com>
* kdb v4.4-2.6.7-rc3-common-1.
2004-06-09 Keith Owens <kaos@sgi.com>
* Namespace clean up. Mark code/variables as static when it is only
used in one file, delete dead code/variables.
* Saved interrupt state requires long, not int.
* kdb v4.4-2.6.7-rc2-common-3.
2004-06-08 Keith Owens <kaos@sgi.com>
* Whitespace clean up, no code changes.
* kdb v4.4-2.6.7-rc2-common-2.
Changelog extract since kdb-v4.4-2.6.7-rc2-i386-1.
2004-06-16 Keith Owens <kaos@sgi.com>
* kdb v4.4-2.6.7-i386-1.
2004-06-10 Keith Owens <kaos@sgi.com>
* kdb v4.4-2.6.7-rc3-i386-1.
2004-06-09 Keith Owens <kaos@sgi.com>
* Namespace clean up. Mark code/variables as static when it is only
used in one file, delete dead code/variables.
* kdb v4.4-2.6.7-rc2-i386-3.
2004-06-08 Keith Owens <kaos@sgi.com>
* Whitespace clean up, no code changes.
* kdb v4.4-2.6.7-rc2-i386-2.
Changelog extract since kdb v4.4-2.6.7-rc2-ia64-1.
2004-06-16 Keith Owens <kaos@sgi.com>
* kdb v4.4-2.6.7-ia64-1.
2004-06-10 Keith Owens <kaos@sgi.com>
* kdb v4.4-2.6.7-rc3-ia64-1.
2004-06-09 Keith Owens <kaos@sgi.com>
* Namespace clean up. Mark code/variables as static when it is only
used in one file, delete dead code/variables.
* Saved interrupt state requires long, not int.
* kdb v4.4-2.6.7-rc2-ia64-3.
2004-06-08 Keith Owens <kaos@sgi.com>
* Whitespace clean up, no code changes.
* kdb v4.4-2.6.7-rc2-2.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Exmh version 2.1.1 10/15/1999
iD8DBQFA0PEHi4UHNye0ZOoRAlkUAJ451FJCUeyPbtwB+o86LoxRjlg82QCfb219
eCxmRqs/pT69UudnvN/2pVA=
=NJMr
-----END PGP SIGNATURE-----
reply other threads:[~2004-06-17 1:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3469.1087435015@kao2.melbourne.sgi.com \
--to=kaos@sgi.com \
--cc=kdb@oss.sgi.com \
--cc=linux-ia64@vger.kernel.org \
--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