From: Lars Marowsky-Bree <lmb@suse.de>
To: GrandMasterLee <masterlee@digitalroadkill.net>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: EVMS is not in 2.5.40, is it?
Date: Tue, 8 Oct 2002 14:29:22 +0200 [thread overview]
Message-ID: <20021008122922.GF5166@marowsky-bree.de> (raw)
In-Reply-To: <1033943522.2437.10.camel@localhost>
On 2002-10-06T17:33:56,
GrandMasterLee <masterlee@digitalroadkill.net> said:
> Just curious, what with all this talk of LVM not working in 2.5.x, and
> that EVMS will work in place of it. I'd like to try it to evaluate it,
> on 2.5.x, that is, but I don't see it in the kernel ATM.
As you have noticed it is not, but the EVMS team has posted repeatedly where
to find the patches for it.
Sincerely,
Lars Marowsky-Brée <lmb@suse.de>
--
Principal Squirrel
Research and Development, SuSE Linux AG
``Immortality is an adequate definition of high availability for me.''
--- Gregory F. Pfister
prev parent reply other threads:[~2002-10-08 12:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-06 22:33 EVMS is not in 2.5.40, is it? GrandMasterLee
2002-10-08 12:29 ` Lars Marowsky-Bree [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=20021008122922.GF5166@marowsky-bree.de \
--to=lmb@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=masterlee@digitalroadkill.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