From: Tomas Szepe <szepe@pinerecords.com>
To: "David S. Miller" <davem@redhat.com>
Cc: netfilter-devel@lists.netfilter.org, linux-kernel@vger.kernel.org
Subject: Re: [TRIVIAL] place IPv4 netfilter submenu where it belongs
Date: Mon, 28 Jul 2003 07:50:15 +0200 [thread overview]
Message-ID: <20030728055015.GA32673@louise.pinerecords.com> (raw)
In-Reply-To: <20030727160942.647707d8.davem@redhat.com>
> [davem@redhat.com]
>
> On Sat, 26 Jul 2003 22:06:46 +0200
> Tomas Szepe <szepe@pinerecords.com> wrote:
>
> > $subj
> >
> > Patch against -bk3.
>
> This doesn't look right at all.
>
> Netfilter is for many protocols other than ipv4 (ipv6, bridging,
> decnet, etc.) so putting it under ipv4 makes not much sense
> to me.
You're right, I'll think about this some more.
--
Tomas Szepe <szepe@pinerecords.com>
next prev parent reply other threads:[~2003-07-28 5:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-26 20:06 [TRIVIAL] place IPv4 netfilter submenu where it belongs Tomas Szepe
2003-07-27 23:09 ` David S. Miller
2003-07-28 5:50 ` Tomas Szepe [this message]
2003-07-29 4:26 ` Tomas Szepe
2003-07-30 5:38 ` David S. Miller
2003-07-30 14:08 ` Harald Welte
2003-07-30 23:54 ` 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=20030728055015.GA32673@louise.pinerecords.com \
--to=szepe@pinerecords.com \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--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