From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: bluca@comedia.it
Cc: linux-lvm@sistina.com, linux-openlvm@nl.linux.org,
AJ Lewis <lewis@sistina.com>, Jes Sorensen <jes@linuxcare.com>,
linux-kernel@vger.kernel.org,
Andreas Dilger <adilger@turbolinux.com>,
Arjan van de Ven <arjanv@redhat.com>, Jens Axboe <axboe@suse.de>,
Martin Kasper Petersen <mkp@linuxcare.com>,
riel@conectiva.com.br, Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [linux-lvm] Re: [repost] Announce: Linux-OpenLVM mailing list
Date: Fri, 20 Apr 2001 03:59:10 -0400 [thread overview]
Message-ID: <3ADFEC4E.BBB210DF@mandrakesoft.com> (raw)
In-Reply-To: <20010420093751.D12971@colombina.comedia.it>
Luca Berra wrote:
> we have some serous problems here.
[...]
> a better lvm (still buggy according to many kernel hackers, but better still),
> which does not get into the kernel for communication reasons. (Alan can you help?
> there is a lot of stuff that goes in -ac before going to mainstream)
I do not think this is a communication problem at all, but a clear lack
of understanding (perhaps willful) on the part of the "LVM maintainers"
about how to get things into the kernel.
linux/Documentation/SubmittingPatches exist to bonk people on the head
if they are screwing up, and it sounds like such is occurring now.
Quite simply,
1) Split up your patches. How many times does it have to be said?
Think ONE CHANGE, ONE PATCH. Big patches full of tons of disparate
changes are impossible to review.
2) (parroting Linus) Open source is about lack of control, not hoarding
code and lording over it. That's why Linus will take a patch from Jens
or another knowledgeable person who says "this LVM code is broken,
-here- is a fix." -- regardless of who the "official" maintainer of the
code is listed as...
[Luca, this is not directed at you, I just used this message as an
opportunity to spout :)]
--
Jeff Garzik | "The universe is like a safe to which there is a
Building 1024 | combination -- but the combination is locked up
MandrakeSoft | in the safe." -- Peter DeVries
next prev parent reply other threads:[~2001-04-20 7:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-20 7:37 [linux-lvm] Re: [repost] Announce: Linux-OpenLVM mailing list Luca Berra
2001-04-20 7:59 ` Jeff Garzik [this message]
[not found] <20010419144815.J10345@sistina.com>
2001-04-20 19:24 ` Heinz J. Mauelshagen
2001-04-20 17:39 ` [linux-lvm] " Wichert Akkerman
-- strict thread matches above, loose matches on Subject: below --
2001-04-19 19:24 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
2001-04-20 1:29 ` Paul Jakma
2001-04-19 17:51 Jes Sorensen
2001-04-19 18:29 ` AJ Lewis
2001-04-19 19:40 ` [linux-lvm] " AJ Lewis
2001-04-19 19:49 ` Alan Cox
2001-04-19 21:25 ` Kurt Garloff
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=3ADFEC4E.BBB210DF@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=adilger@turbolinux.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arjanv@redhat.com \
--cc=axboe@suse.de \
--cc=bluca@comedia.it \
--cc=jes@linuxcare.com \
--cc=lewis@sistina.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