From: Luca Berra <bluca@comedia.it>
To: linux-lvm@sistina.com, linux-openlvm@nl.linux.org
Cc: 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 09:37:51 +0200 [thread overview]
Message-ID: <20010420093751.D12971@colombina.comedia.it> (raw)
Fuck! I hate these things early in the morning.
what gets me extremely pissed in the whole business is that i don't
believe that splitting the mailing list is the solution to LVM problems.
Escpecially since we have a number of lusers of lwm at the time being.
I believe sistina is mostly at fault there, not for the mailing list issue
(i really don't believe people getting kicked out, while the moderation
messages are probably due to mailman braindamage)
but for political reasons (stop making it look as a sistina-only project, it pisses
everyone)
we have some serous problems here.
an lvm in the kernel which is badly broken(tm)
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)
A development model where only sistina people have access to cvs. This is bad, has the only
effect of pissing off people like Andreas which has been feeding patches and good ideas for
many months now, besides it leads to people having their own lvm tree, so everybody is
testing their development version, which has nothing to do with the version in the
goddamned kernel.
now what i propose is (some has already been said):
lets's vote for which mailing list we want to keep (and everybody accept the result)
open the goddam cvs to hackers that request access to it, you can use different branches
and do code freezes with cvs, so it won't hurt releases schedules.
try to ship the most evident bugfixes from cvs to linus, please all long-time kernel hakcers
who got involved in this help do this.
open up also the decision process (IOP 11 in beta5 and IOP 10 back in beta6
could not have happened if somebody eles knew about the IOP change.)
Regards,
L.
(Sorry for the big CC list, but i dunno who is subscribed to what anymore)
--
Luca Berra -- bluca@comedia.it
Communication Media & Services S.r.l.
/"\
\ / ASCII RIBBON CAMPAIGN
X AGAINST HTML MAIL
/ \
next reply other threads:[~2001-04-20 7:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-20 7:37 Luca Berra [this message]
2001-04-20 7:59 ` [linux-lvm] Re: [repost] Announce: Linux-OpenLVM mailing list 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
-- 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=20010420093751.D12971@colombina.comedia.it \
--to=bluca@comedia.it \
--cc=adilger@turbolinux.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arjanv@redhat.com \
--cc=axboe@suse.de \
--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