All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jes Sorensen <jes@sunsite.dk>
To: Christoph Hellwig <hch@caldera.de>
Cc: David Balazic <david.balazic@uni-mb.si>, linux-kernel@vger.kernel.org
Subject: Re: IBMs LVM ?
Date: 27 Sep 2001 21:36:19 +0200	[thread overview]
Message-ID: <d3u1xov32k.fsf@lxplus015.cern.ch> (raw)
In-Reply-To: <3B9E255C.8943D6BB@uni-mb.si> <200109111526.f8BFQLr25266@ns.caldera.de> <20010911115713.D29347@turbolinux.com> <20010911200633.A5816@caldera.de>
In-Reply-To: Christoph Hellwig's message of "Tue, 11 Sep 2001 20:06:33 +0200"

>>>>> "Christoph" == Christoph Hellwig <hch@caldera.de> writes:

Christoph> On Tue, Sep 11, 2001 at 11:57:13AM -0600, Andreas Dilger
Christoph> wrote:
>> Do you have a specific complaint?  The current LVM kernel code
>> isn't all that robust either (and the user-space code is not very
>> pretty).

Christoph> Please take a barf-bag, look at the code, look at the
Christoph> unneded abstrations, look at the uneeded interfaces, look
Christoph> at the code-duplication, look at the over-engineering.

At least the IBM guys seem interested in listening and taking
code/suggestions from the community. There was a fairly productive BOF
at OLS a couple of months ago. Thats a lot more than we can say about
the current LVM.

Jes

  parent reply	other threads:[~2001-09-27 19:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-11 14:53 IBMs LVM ? David Balazic
2001-09-11 15:26 ` Christoph Hellwig
2001-09-11 17:57   ` Andreas Dilger
2001-09-11 18:06     ` Christoph Hellwig
2001-09-11 19:15       ` Andreas Dilger
2001-09-11 19:57         ` Christoph Hellwig
2001-09-27 19:36       ` Jes Sorensen [this message]
2001-09-27 23:03         ` Alan Cox
     [not found] <200109142155.f8ELtVi03827@shay.ecn.purdue.edu>
2001-09-20 11:57 ` IBMs LVM? Christoph Hellwig
2001-09-20 16:05   ` Andreas Dilger
2001-09-20 16:12     ` Steven Whitehouse

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=d3u1xov32k.fsf@lxplus015.cern.ch \
    --to=jes@sunsite.dk \
    --cc=david.balazic@uni-mb.si \
    --cc=hch@caldera.de \
    --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 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.