From: Jens Axboe <axboe@suse.de>
To: AJ Lewis <lewis@sistina.com>
Cc: Jes Sorensen <jes@linuxcare.com>,
linux-kernel@vger.kernel.org, linux-openlvm@nl.linux.org,
Arjan van de Ven <arjanv@redhat.com>,
Martin Kasper Petersen <mkp@linuxcare.com>,
riel@conectiva.com.br, linux-lvm@sistina.com
Subject: Re: [repost] Announce: Linux-OpenLVM mailing list
Date: Thu, 19 Apr 2001 20:48:19 +0200 [thread overview]
Message-ID: <20010419204819.D30135@suse.de> (raw)
In-Reply-To: <d37l0gvkuf.fsf@lxplus015.cern.ch> <20010419132927.D10345@sistina.com>
In-Reply-To: <20010419132927.D10345@sistina.com>; from lewis@sistina.com on Thu, Apr 19, 2001 at 01:29:27PM -0500
On Thu, Apr 19 2001, AJ Lewis wrote:
> It is unfortunate that this could not have been resolved in a more mature
> manner. Saying "I don't like the way somebody is doing something. I won't
> bother to talk to them about it, I'll just flame them and try to undermine
> their work." is not acceptable. It would have been nice if you'd actually
> tried to work this out instead of handling it this way.
LVM concerns us all now that it is not just an addon, but actually a
part of the kernel. Rejecting mails and reports from users and
developers who just might be able to lend you a hand fixing bugs, is not
just counter productive it's downright rude!
Besides, I didn't think the posting was flame material at all. If
nothing else, it's a wake up call.
--
Jens Axboe
next prev parent reply other threads:[~2001-04-19 18:49 UTC|newest]
Thread overview: 45+ 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 [this message]
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
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 1:36 Dan Kegel
2001-04-20 9:33 Constantine Gavrilov
[not found] <20010419144815.J10345@sistina.com>
2001-04-20 19:24 ` Heinz J. Mauelshagen
2001-04-20 18:04 ` Alan Cox
2001-04-20 18:25 ` Jens Axboe
2001-04-23 10:16 ` Heinz J. Mauelshagen
2001-04-23 9:50 ` Heinz J. Mauelshagen
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=20010419204819.D30135@suse.de \
--to=axboe@suse.de \
--cc=arjanv@redhat.com \
--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