From: Jose Luis Domingo Lopez <linux-kernel@24x7linux.com>
To: Guillaume Boissiere <boissiere@adiglobal.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [STATUS 2.6] August 08, 2003
Date: Sat, 9 Aug 2003 12:00:13 +0200 [thread overview]
Message-ID: <20030809100013.GA1965@localhost> (raw)
In-Reply-To: <3F33F7AB.29994.226855A@localhost>
On Friday, 08 August 2003, at 19:19:07 -0400,
Guillaume Boissiere wrote:
> It's been a while since the last status update. Tons of bug fixes
> have made their way into the 2.6.0-test tree, but (impressively)
> few new features.
> Security folks will be happy to know that SELinux was merged and
> will be part of 2.6.0-test3.
>
I think your list is missing the inclusion (in the 2.5.75 -> 2.6.0-test1
timeframe) of Linux Virtual Server (wwww.linuxvirtualserver.org).
Regards,
--
Jose Luis Domingo Lopez
Linux Registered User #189436 Debian Linux Sid (Linux 2.6.0-test2-mm2)
prev parent reply other threads:[~2003-08-09 10:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-08 23:19 [STATUS 2.6] August 08, 2003 Guillaume Boissiere
2003-08-09 10:00 ` Jose Luis Domingo Lopez [this message]
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=20030809100013.GA1965@localhost \
--to=linux-kernel@24x7linux.com \
--cc=boissiere@adiglobal.com \
--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