From: Joe Thornber <thornber@btconnect.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] What is the state of lvm in 2.4.15-pre3?
Date: Mon Nov 12 02:50:02 2001 [thread overview]
Message-ID: <20011112085203.C535@btconnect.com> (raw)
In-Reply-To: <20011112004154.EF77AA3AE1@oscar.casa.dyndns.org>; from tomlins@cam.org on Sun, Nov 11, 2001 at 07:41:52PM -0500
On Sun, Nov 11, 2001 at 07:41:52PM -0500, Ed Tomlinson wrote:
> Hi
>
> I noticed that pre3 contained a large update to lvm. With this update
> what is the state of lvm? What set of utilites should be used with
> pre3 (rc4?).
I've just had a look; a cursory inspection suggests this is a full
merge with the code in the -ac tree. In short this is very up to date,
only omitting a couple of Andreas Dilgers more recent changes.
- Joe
prev parent reply other threads:[~2001-11-12 2:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-11 18:40 [linux-lvm] What is the state of lvm in 2.4.15-pre3? Ed Tomlinson
2001-11-12 2:37 ` Patrick Caulfield
2001-11-12 2:50 ` Joe Thornber [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=20011112085203.C535@btconnect.com \
--to=thornber@btconnect.com \
--cc=linux-lvm@sistina.com \
/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;
as well as URLs for NNTP newsgroup(s).