From: Christoph Hellwig <hch@ns.caldera.de>
To: linux-lvm@sistina.com
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Jes Sorensen <jes@linuxcare.com>,
linux-kernel@vger.kernel.org, linux-openlvm@nl.linux.org,
Arjan van de Ven <arjanv@redhat.com>, Jens Axboe <axboe@suse.de>,
Martin Kasper Petersen <mkp@linuxcare.com>,
riel@conectiva.com.br
Subject: Re: [linux-lvm] Re: [repost] Announce: Linux-OpenLVM mailing list
Date: Thu, 19 Apr 2001 21:55:57 +0200 [thread overview]
Message-ID: <20010419215557.A7477@caldera.de> (raw)
In-Reply-To: <20010419142400.E10345@sistina.com> <200104191945.f3JJjKRn015661@webber.adilger.int>
In-Reply-To: <200104191945.f3JJjKRn015661@webber.adilger.int>; from adilger@turbolinux.com on Thu, Apr 19, 2001 at 01:45:20PM -0600
On Thu, Apr 19, 2001 at 01:45:20PM -0600, Andreas Dilger wrote:
> I don't think that the subscription is necessarily the only issue. I'm
> subscribed to all of the LVM mailing lists, and still a lot of what I
> submit (legitimate bug fixes, and not just features/code cleanup) does
> not get added to CVS.
Just alone the fact that you as number one submitter of LVM-bugfixes since
at least 0.8 do not get CVS write access is a sign of closedness for me.
But we discussed that on the sistina list.
> Yes, the no-possible-harm patches like man pages
> went in, but not other stuff. Also, it doesn't appear that any of the
> LVM changes are making it into the stock kernel, which is basically a
> recepie for disaster.
100% True. A few days ago I looke at the LVM patches to see what parts
of it could be fed to Linus in small pieces - but it's such a _huge_
mixture of bugfixes, cleanups and move-arounds that it looks pretty
much impossible.
> Basically, I'm at the point where trying to create clean patches from my
> LVM source tree to apply to CVS is so much work it is hardly worth it.
IMHO wou should just put _your_ tree on a sever and submit it (in pieces)
to Linus. AFAIK all serious users of LVM have used you're patched versions.
Maybe openlvm is a good hood for such a project?
> I'm seriously looking at devoting the time I used to spend on LVM to the
> EVMS project instead. They (appear to) have in-kernel LVM support working
> already, so no user tools needed for VG/LV activation. Granted, they don't
> yet have tools to create/modify VG/LVs, but I think I can help them there.
Yes - when looking at what code they produces it looks a _lot_ cleaner than
Linux-LVM and while the papers had serious signs of Overengeering the
actual code looks very good to me - it could just get a little better
integrated with the main kernel, but that's a 2.5 issue.
Christoph
--
Of course it doesn't work. We've performed a software upgrade.
next prev parent reply other threads:[~2001-04-19 19:58 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-19 17:51 [repost] Announce: Linux-OpenLVM mailing list Jes Sorensen
2001-04-19 18:29 ` AJ Lewis
2001-04-19 18:34 ` Jeff Garzik
2001-04-19 18:35 ` Rik van Riel
2001-04-24 14:58 ` Heinz J. Mauelshagen
2001-04-19 18:48 ` Jens Axboe
2001-04-24 14:54 ` Heinz J. Mauelshagen
2001-04-19 19:02 ` Alan Cox
2001-04-19 19:24 ` AJ Lewis
2001-04-19 19:33 ` Jens Axboe
2001-04-19 19:46 ` Martin K. Petersen
2001-04-24 15:00 ` Heinz J. Mauelshagen
2001-04-19 19:35 ` Jes Sorensen
2001-04-19 19:44 ` AJ Lewis
2001-04-19 19:45 ` [linux-lvm] " Andreas Dilger
2001-04-19 19:51 ` Alan Cox
2001-04-19 19:53 ` Rik van Riel
2001-04-19 19:53 ` AJ Lewis
2001-04-19 19:56 ` Jens Axboe
2001-04-19 20:03 ` Alan Cox
2001-04-19 21:52 ` Miles Lane
2001-04-19 20:09 ` Jeff Garzik
2001-04-19 20:16 ` AJ Lewis
2001-04-20 10:34 ` Patrick Caulfield
2001-04-20 0:41 ` Andreas Dilger
2001-04-19 19:55 ` Christoph Hellwig [this message]
2001-04-20 1:29 ` Paul Jakma
2001-04-19 20:33 ` Miles Lane
2001-04-20 12:36 ` Doug McNaught
2001-04-20 22:55 ` Matti Aarnio
2001-04-21 20:45 ` Rik van Riel
2001-04-19 19:17 ` Jes Sorensen
2001-04-19 19:26 ` AJ Lewis
2001-04-19 19:40 ` Jes Sorensen
2001-04-19 19:19 ` Martin K. Petersen
2001-04-19 19:40 ` [linux-lvm] " AJ Lewis
2001-04-19 19:49 ` Alan Cox
2001-04-19 21:25 ` Kurt Garloff
-- strict thread matches above, loose matches on Subject: below --
2001-04-20 7:37 Luca Berra
2001-04-20 7:59 ` Jeff Garzik
[not found] <20010419144815.J10345@sistina.com>
2001-04-20 19:24 ` Heinz J. Mauelshagen
2001-04-20 17:39 ` [linux-lvm] " Wichert Akkerman
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=20010419215557.A7477@caldera.de \
--to=hch@ns.caldera.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arjanv@redhat.com \
--cc=axboe@suse.de \
--cc=jes@linuxcare.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-lvm@sistina.com \
--cc=linux-openlvm@nl.linux.org \
--cc=mkp@linuxcare.com \
--cc=riel@conectiva.com.br \
/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