netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Harald Welte <laforge@netfilter.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: Linux Netdev List <netdev@oss.sgi.com>,
	Netfilter Development Mailinglist
	<netfilter-devel@lists.netfilter.org>
Subject: Re: [PATCH 2.6] iptables CLUSTERIP target
Date: Thu, 21 Oct 2004 11:12:29 +0200	[thread overview]
Message-ID: <20041021091229.GA3551@sunbeam.de.gnumonks.org> (raw)
In-Reply-To: <20041021075530.GA1278@infradead.org>

[-- Attachment #1: Type: text/plain, Size: 1019 bytes --]

On Thu, Oct 21, 2004 at 08:55:30AM +0100, Christoph Hellwig wrote:
> btw, please stop crossposting to public and private lists, or even better
> allow posting to netfiler-devel without subscription like every sane list
> allows to.

We allow posting, your posting will just await moderator approval.  Our
listmaster usuall checks more than once per day.  

Developers who happen to post more often (like davem) will be added to
an explicit sender filter.

Unfortunately wi didn't find any other reliable way to catch all the
spam we receive, sorry.  And yes, we already run spamassassin, as well
as mimetype-based and HTML filters.

-- 
- Harald Welte <laforge@netfilter.org>             http://www.netfilter.org/
============================================================================
  "Fragmentation is like classful addressing -- an interesting early
   architectural error that shows how much experimentation was going
   on while IP was being designed."                    -- Paul Vixie

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-10-21  9:12 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-20 22:38 [PATCH 2.6] iptables CLUSTERIP target Harald Welte
2004-10-20 23:18 ` YOSHIFUJI Hideaki / 吉藤英明
2004-10-21  4:40   ` David S. Miller
2004-10-21  7:44 ` Christoph Hellwig
2004-10-21  7:55 ` Christoph Hellwig
2004-10-21  9:12   ` Harald Welte [this message]
2004-10-21  9:40     ` Herbert Xu
2004-10-21 11:05     ` bert hubert
2004-10-21 13:03       ` Harald Welte
2004-10-21 13:33         ` Lars Marowsky-Bree
2004-10-21 14:25           ` Harald Welte
2004-10-21 15:08             ` bert hubert
2004-10-21 21:31             ` Allowing netlink_family to be any integer (was: [PATCH 2.6] iptables CLUSTERIP target) Herbert Xu
2004-10-21 22:53               ` Thomas Graf
2004-10-21 23:02                 ` Allowing netlink_family to be any integer Ben Greear
2004-10-22 12:25                 ` Allowing netlink_family to be any integer (was: [PATCH 2.6] iptables CLUSTERIP target) Herbert Xu
2004-10-22 12:53                   ` jamal
2004-10-22 11:29               ` jamal
2004-10-22 11:39                 ` Herbert Xu
2004-10-22 12:19                   ` jamal
2004-10-22 12:32                     ` Evgeniy Polyakov
2004-10-22 23:05               ` David S. Miller
2004-10-22 23:16                 ` Herbert Xu
2004-10-26  3:27                   ` David S. Miller
2004-10-21 16:36 ` [PATCH 2.6] iptables CLUSTERIP target, seq_file version Harald Welte
2004-10-21 17:44   ` jamal
2004-10-21 18:03     ` Harald Welte
2004-10-21 18:41       ` Henrik Nordstrom
2004-10-22  5:52   ` David S. Miller

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=20041021091229.GA3551@sunbeam.de.gnumonks.org \
    --to=laforge@netfilter.org \
    --cc=hch@infradead.org \
    --cc=netdev@oss.sgi.com \
    --cc=netfilter-devel@lists.netfilter.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;
as well as URLs for NNTP newsgroup(s).