From: "Robert L. Harris" <Robert.L.Harris@rdlg.net>
To: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Diff chart?
Date: Wed, 9 Apr 2003 10:58:07 -0400 [thread overview]
Message-ID: <20030409145807.GE28799@rdlg.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 843 bytes --]
Out of curiosity. Is there any chart or list that would show the
current state of 2.4 compared to 2.5? Not the stability or # of bugs,
but feature changes, security changes, etc? Things I can show
management types of what is coming up?
A first glance at the 2.5 about had me drooling and I'd like to get
management thinking that 2.6 is going to be a beautiful thing, not just
a service patch.
Robert
:wq!
---------------------------------------------------------------------------
Robert L. Harris | PGP Key ID: E344DA3B
@ x-hkp://pgp.mit.edu
DISCLAIMER:
These are MY OPINIONS ALONE. I speak for no-one else.
Diagnosis: witzelsucht
IPv6 = robert@ipv6.rdlg.net http://ipv6.rdlg.net
IPv4 = robert@mail.rdlg.net http://www.rdlg.net
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2003-04-09 14:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-09 14:58 Robert L. Harris [this message]
2003-04-09 15:22 ` Diff chart? Maciej Soltysiak
2003-04-09 15:24 ` Robert L. Harris
2003-04-09 15:50 ` Dave Jones
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=20030409145807.GE28799@rdlg.net \
--to=robert.l.harris@rdlg.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