From: "Guillaume Boissiere" <boissiere@adiglobal.com>
To: linux-kernel@vger.kernel.org
Subject: [STATUS 2.5] January 15, 2003
Date: Wed, 15 Jan 2003 17:36:38 -0500 [thread overview]
Message-ID: <3E259C26.5828.1912568@localhost> (raw)
Probably the most important thing since last week is the merge of Andrew
Morton's work to remove the last remaining sources of high scheduling
latency aka "Linux 2.6, multimedia OS".
On the bugzilla side, 155 bugs and counting. And there are lots and lots
of compile warnings since the introduction of the deprecated keyword
(see http://www.osdl.org/archive/cherry/stability/ John Cherry's excellent
page for details).
As usual, let me know if anything is missing or inaccurate on the status
page. Cheers,
-- Guillaume
The status page: http://www.kernelnewbies.org/status
Bugzilla: http://bugzilla.kernel.org/
reply other threads:[~2003-01-15 22:28 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=3E259C26.5828.1912568@localhost \
--to=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