From: Denis Vlasenko <vda@ilport.com.ua>
To: gene.heskett@verizononline.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.14.5
Date: Wed, 28 Dec 2005 10:02:35 +0200 [thread overview]
Message-ID: <200512281002.35214.vda@ilport.com.ua> (raw)
In-Reply-To: <200512271540.08809.gene.heskett@verizon.net>
On Tuesday 27 December 2005 22:40, Gene Heskett wrote:
> On Tuesday 27 December 2005 15:01, Grant Coady wrote:
> >On Mon, 26 Dec 2005 19:33:35 -0800 (PST), "David S. Miller"
> <davem@davemloft.net> wrote:
> >>Please report it to the netfilter mailing list, which is
> >>where the netfilter developers listen and can attend to
> >>your report.
> >>
> >>Thanks a lot.
> >
> >Why bother?
> >
> >"
> >Your request to the netfilter-devel mailing list
> >
> > Posting of your message titled "Re: Linux 2.6.14.5"
> >
> >has been rejected by the list moderator. The moderator gave the
> >following reason for rejecting your request:
> >
> >"Non-members are not allowed to post messages to this list."
> >
> >Any questions or comments should be directed to the list
> > administrator at:
> >
> > netfilter-devel-owner@lists.netfilter.org
> >"
> >
> >Grant.
> >
> I too have been rejected at that address. Like Grant, why bother seems
> to be the appropriate response. If they want to here soonest when
> there is a problem, then the moderator should clear what is obviously
> not a spam message to the list in a reasonable time frame. Its never
> happened to me but once and I was bascily told to "go away little
> boy."
Moderators of mailing lists scale badly compared to number
China-hosted hosts spewing tons of TCP traffic to port 25...
> I'm already subbed to about 40 lists, and while there are some I could
> drop to make room for others, my interests are best described as
> ecclectic.
>
> If the netfilter folks want to be artificialy quiet, shrug.
I guess they prefer bugs to be reported thru bugzilla.
I just reported one yesterday.
--
vda
next prev parent reply other threads:[~2005-12-28 8:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-27 0:53 Linux 2.6.14.5 Greg KH
2005-12-27 0:54 ` Greg KH
2005-12-27 3:06 ` Grant Coady
2005-12-27 3:33 ` David S. Miller
2005-12-27 20:01 ` Grant Coady
2005-12-27 20:40 ` Gene Heskett
2005-12-28 8:02 ` Denis Vlasenko [this message]
2005-12-28 15:51 ` Lee Revell
2005-12-27 3:46 ` [stable] " Greg KH
2005-12-27 5:28 ` Grant Coady
2005-12-27 4:48 ` Patrick McHardy
2005-12-27 5:45 ` Grant Coady
2005-12-27 5:17 ` Willy Tarreau
2005-12-27 5:42 ` Grant Coady
2005-12-27 5:45 ` Willy Tarreau
2005-12-27 5:59 ` Grant Coady
2005-12-27 6:07 ` Phil Oester
2005-12-27 6:41 ` Yasuyuki KOZAKAI
2005-12-27 6:51 ` Grant Coady
[not found] ` <200512270641.jBR6f6vt024777@toshiba.co.jp>
2005-12-27 6:58 ` Willy Tarreau
2005-12-27 7:12 ` Yasuyuki KOZAKAI
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=200512281002.35214.vda@ilport.com.ua \
--to=vda@ilport.com.ua \
--cc=gene.heskett@verizononline.net \
--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