From: Joe Thornber <joe@fib011235813.fsnet.co.uk>
To: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux 2.5.25 (and LVM)
Date: Mon, 8 Jul 2002 09:43:15 +0100 [thread overview]
Message-ID: <20020708084315.GA1387@fib011235813.fsnet.co.uk> (raw)
In-Reply-To: <20020706135412.GA19227@merlin.emma.line.org>
On Sat, Jul 06, 2002 at 03:54:12PM +0200, Matthias Andree wrote:
> On Fri, 05 Jul 2002, Linus Torvalds wrote:
>
> > More merges all over the map - ppc, scsi, USB, kbuild, input drivers etc.
>
> Did the LVM guys (are you listening?) tell anything if they were about
> to go fix the current 2.5 LVM breakage? Or does EVMS work on 2.5 instead?
I'll say this yet again:
Heinz Mauelshagen is maintaining LVM1.0.x on 2.4 kernels. This is for
bug fixes only, no new features will be added.
Alasdair Kergon, Patrick Caulfield and myself are working on the more
generic device-mapper driver for both 2.4/2.5. Initially we have
concentrated on 2.4, this driver is now very stable IMO (I would
certainly trust my data to it in preference to LVM1).
I will post a URL to the 2.5 patch at some point this week.
There is no intention to maintain the broken design that is LVM1 in
the 2.5 series - we do not have the spare resources to waste.
- Joe
next prev parent reply other threads:[~2002-07-08 7:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-05 23:54 linux 2.5.25 Linus Torvalds
2002-07-06 5:35 ` Albert D. Cahalan
2002-07-06 8:17 ` [patch] Typo fixes in input code Brad Hards
2002-07-06 17:48 ` James Simmons
2002-07-07 2:22 ` Brad Hards
2002-07-08 11:08 ` Vojtech Pavlik
2002-07-06 13:54 ` linux 2.5.25 (and LVM) Matthias Andree
2002-07-08 8:43 ` Joe Thornber [this message]
2002-07-08 8:40 ` Alexander Viro
2002-07-08 1:04 ` linux 2.5.25 Tim Pepper
2002-07-08 12:44 ` [PATCH] 2.5.25 end_request trivia Martin Dalecki
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=20020708084315.GA1387@fib011235813.fsnet.co.uk \
--to=joe@fib011235813.fsnet.co.uk \
--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
all inboxes | Powered by JetHome®