public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Constantine Gavrilov <const-g@optibase.com>
To: lewis@sistina.com
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [repost] Announce: Linux-OpenLVM mailing list
Date: Fri, 20 Apr 2001 12:33:16 +0300	[thread overview]
Message-ID: <3AE0025C.3020107@optibase.com> (raw)

 > Hmm...i guess there is a communication issue here.  It sounds like the
 >  message that our ML server was sending was misleading.  We were not
 > rejecting mail because of content.  The ML server was rejecting it 
because
 > the address was not subscribed.  Our idea was that we don't want spam.
 > If it's completely unmoderated, then we will get a *lot* of spam.

I do not think there is a miscommunication here. First, someone gets an 
e-mail saying that your message "waits for moderator's approval". Then 
you get a message saying that your "message was rejected by the 
moderator because you are not subscribed to the list".

Mind it, those were bug reports, not spam. I took your beta code, tested 
it, saw real bugs and problems and wrote bug reports  BECAUSE YOU 
INCOURAGE PEOPLE TO DO SO AND GIVE THOSE EMAILS IN THE DOCUMENTATION!!!

There is no place in the source tree docs that say the list is 
moderated.  It it had said so, I would have not wasted my time. I felt 
really pissed off for waisting my time. BTW, other e-mails given in the 
documentation just bounce. If you do not want people sending bug 
reports, update your documentation. It is not polite to make people 
waste their time!

-- 
----------------------------------------
Constantine Gavrilov
Linux Leader
Optibase Ltd
7 Shenkar St, Herzliya 46120, Israel
Phone: (972-9)-970-9140
Fax:   (972-9)-958-6099
----------------------------------------


             reply	other threads:[~2001-04-20  9:33 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-20  9:33 Constantine Gavrilov [this message]
     [not found] <20010419144815.J10345@sistina.com>
2001-04-20 19:24 ` [repost] Announce: Linux-OpenLVM mailing list 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
  -- strict thread matches above, loose matches on Subject: below --
2001-04-20  1:36 Dan Kegel
2001-04-19 17:51 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 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

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=3AE0025C.3020107@optibase.com \
    --to=const-g@optibase.com \
    --cc=lewis@sistina.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox