From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Mike Fedyk <mfedyk@matchmail.com>
Cc: m.c.p@wolk-project.de, linux-kernel@vger.kernel.org,
wolk-devel@lists.sourceforge.net,
wolk-announce@lists.sourceforge.net
Subject: Re: [ANNOUNCE] WOLK v1.0 for Kernel v2.6.3
Date: Thu, 26 Feb 2004 13:10:48 -0800 [thread overview]
Message-ID: <20040226131048.54885fca.rddunlap@osdl.org> (raw)
In-Reply-To: <403E5853.2080702@matchmail.com>
On Thu, 26 Feb 2004 12:34:27 -0800 Mike Fedyk wrote:
| Marc-Christian Petersen wrote:
| > o added: extend memstats (me)
|
| What does this do?
|
| > o added: Application Layer 7 Packet Classifier v0.4.1b (Ethan Sommer)
|
| Where can I find more info on this?
|
| > o added: initrd support for cramfs (Herbert Xu)
|
| I'd love to see this merged upstream.
Is that like this?
http://linux.bkbits.net:8080/linux-2.5/cset@1.1500.8.45?nav=index.html|ChangeSet@-4w
--
~Randy
next prev parent reply other threads:[~2004-02-26 21:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-26 18:24 [ANNOUNCE] WOLK v1.0 for Kernel v2.6.3 Marc-Christian Petersen
2004-02-26 20:34 ` Mike Fedyk
2004-02-26 21:10 ` Randy.Dunlap [this message]
2004-02-26 21:59 ` Jose Luis Domingo Lopez
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=20040226131048.54885fca.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.c.p@wolk-project.de \
--cc=mfedyk@matchmail.com \
--cc=wolk-announce@lists.sourceforge.net \
--cc=wolk-devel@lists.sourceforge.net \
/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