All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael Ju. Tokarev" <mjt@tls.msk.ru>
To: Heinz Mauelshagen <mauelshagen@sistina.com>
Cc: linux-lvm@msede.com
Subject: Re: [linux-lvm] Is LVM dead ?
Date: Sun, 22 Oct 2000 02:31:21 +0400	[thread overview]
Message-ID: <39F21939.682BCCF7@tls.msk.ru> (raw)
In-Reply-To: 20001020220300.B22203@homer.sistina.com

Heinz Mauelshagen wrote:
> 
> Michael,
> 
> as mentioned on this list a couple of days ago, LVM 0.9 is going to be
> released early november.

I follow this list for about a year now.  There was some references
last month to 0.9, two of them was yours.  But that 0.9 is like a
cloud that maybe here or maybe not.  In contrast, demands for
bugfixes are high for some months already.  Most important for
many users are bugfixes -- with current features lvm already
very useful, but probably not so useful with bugs and great features.
I say here about already well-known bugs that are serious enouth.
Can someone count how many people debugged existing bugs that
was already fixed in some 0.9 code? :(  Look to list: there is
a loop like:

  can someone point me to lvm for kernel 2.2.15 (2.2.16, 2.2.17,...)?
    -- yes, it is there and there
       -- thanks
  oh, there is a bug in lvm there and there.  Here is a patch.
    -- yes, it is a known bug, patch already there and there and there.
  oh, there is another bug, patch included.
    -- yes, it is also a known bug, patch can be found...

And so on.  Most people just stuck on applying kernel patches, as
current kernel is different compared to 2.2.13 one...

Great thanks to Andeas Dilger who maintains his version of all
needed stuff -- I'm shure that this work saved a lot of the above
cycles.

> It will for eg. contain persistent and resizable snapshots.
> 
> If you have any feature enhancements, bug fixes or code to supply,
> Please feel free to discuss them on this list.

What really needed is a collection of all patches or, preferrably,
one (maybe inetrim) release, with a point to it from
linux.msede.com/lvm.

[my flaws skipped]
> > I'm sorry, I'm really very sorry for this all if I'm wrong.
> > This is just my impression, nothing more.  And I apologize,
> > really, if I'm wrong.
> 
> You should.
>
> > But -- who can demonstrate that I'm wrong ??? :(((((((((
> 
> Hopefully i was.

Ok.  I greatly apologize, Heinz!  Excuse me please.

But you should agree that from "outside" view things
_may_ looks like I described.  I has some talks with
my friends today, and some of them have the same
impressions...  And look -- situation is trivial
to reslove, and many people will be glad to help.

Also I'm shure that someone will be glad/interested
to help with 0.9 release implementation...

Again, Excuse me please, Heinz and all!

Regards,
 Michael.

  parent reply	other threads:[~2000-10-21 22:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-20 21:08 [linux-lvm] Is LVM dead ? Michael Tokarev
2000-10-21  3:03 ` Heinz Mauelshagen
2000-10-21  3:49   ` Andi Kleen
2000-10-21  9:19     ` Paul Jakma
2000-10-21  9:21     ` Jan Niehusmann
2000-10-23 23:37       ` Andreas Dilger
2000-10-21 22:31   ` Michael Ju. Tokarev [this message]
2000-10-25  1:48 ` Andreas Dilger

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=39F21939.682BCCF7@tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=linux-lvm@msede.com \
    --cc=mauelshagen@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.