linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shawn <core@enodev.com>
To: Michael Clark <michael@metaparadigm.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Alexander Viro <viro@math.psu.edu>,
	Andreas Dilger <adilger@clusterfs.com>,
	Lars Marowsky-Bree <lmb@suse.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Remove LVM from 2.5 (resend)
Date: Thu, 3 Oct 2002 10:07:02 -0500	[thread overview]
Message-ID: <20021003100702.C32461@q.mn.rr.com> (raw)
In-Reply-To: <3D9C4FA8.10201@metaparadigm.com>; from michael@metaparadigm.com on Thu, Oct 03, 2002 at 10:09:44PM +0800

On 10/03, Michael Clark said something like:
> On 10/03/02 20:38, Alan Cox wrote:
> > On Thu, 2002-10-03 at 06:50, Michael Clark wrote:
> > 
> >>>... and you don't need EVMS for that.
> >>
> >>But EVMS would be an excellent substitute in the mean time.
> >>
> >>Better to having something excellent now than something perfect but
> >>too late.

This statement is misleading; in no way is EVMS intended as an
interim solution to a problem addressed easier in other ways. It's
a fundamental change which happens to address certain critical issues
and also adds functionality whiz-bangs.

> > You can see who around here has maintained kernel code and who hasnt.
> > You don't want a substitute in the mean time, because then you have to
> > get rid of it
> 
> Like LVM ;)

Not quite...

> /me submits to the masters and waits in subjugation.
> 
> Just hoping for good Volume Manager in 2.6 and EVMS looks good
> to me from an end user perspective, and also seems quite timely.

Me too.

--
Shawn Leas
core@enodev.com

I had a friend who was a clown...  when he died, all his friends went to the
funeral in one car...
						-- Stephen Wright

  reply	other threads:[~2002-10-03 15:02 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-01 14:06 [PATCH] Remove LVM from 2.5 (resend) Joe Thornber
2002-10-01 14:15 ` Alexander Viro
2002-10-01 14:52   ` venom
2002-10-01 15:48     ` Dave Jones
2002-10-01 16:06       ` Jens Axboe
2002-10-01 16:35         ` Joe Thornber
2002-10-01 16:41           ` Jens Axboe
2002-10-01 23:19             ` venom
2002-10-01 18:42       ` Lars Marowsky-Bree
2002-10-02  1:00         ` Alan Cox
2002-10-02  4:24           ` Theodore Ts'o
2002-10-02 13:34             ` Alan Cox
2002-10-02 14:54               ` Lars Marowsky-Bree
2002-10-02 17:09                 ` Alan Cox
2002-10-02 22:29                   ` Lars Marowsky-Bree
2002-10-02 22:46                     ` Alan Cox
2002-10-02 23:14                       ` Andreas Dilger
2002-10-02 23:22                         ` Alexander Viro
2002-10-03  5:50                           ` Michael Clark
2002-10-03 12:38                             ` Alan Cox
2002-10-03 14:09                               ` Michael Clark
2002-10-03 15:07                                 ` Shawn [this message]
2002-10-03 15:22                                   ` Michael Clark
2002-10-06  5:05                                     ` GrandMasterLee
2002-10-01 19:12       ` Matthias Andree
2002-10-01 23:25         ` venom
2002-10-01 17:09   ` Status of InterMezzo in 2.5 Andreas Dilger
2002-10-01 14:40 ` [PATCH] Remove LVM from 2.5 (resend) Jens Axboe
2002-10-01 14:54   ` Joe Thornber

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=20021003100702.C32461@q.mn.rr.com \
    --to=core@enodev.com \
    --cc=adilger@clusterfs.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lmb@suse.de \
    --cc=michael@metaparadigm.com \
    --cc=viro@math.psu.edu \
    /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).