From: Harald Welte <laforge@netfilter.org>
To: "David S. Miller" <davem@redhat.com>
Cc: Tomas Szepe <szepe@pinerecords.com>,
netfilter-devel@lists.netfilter.org,
linux-kernel@vger.kernel.org
Subject: Re: [TRIVIAL] place IPv4 netfilter submenu where it belongs
Date: Wed, 30 Jul 2003 16:08:13 +0200 [thread overview]
Message-ID: <20030730140813.GC4553@sunbeam.de.gnumonks.org> (raw)
In-Reply-To: <20030729223802.1d670476.davem@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 905 bytes --]
Hi Dave!
On Tue, Jul 29, 2003 at 10:38:02PM -0700, David S. Miller wrote:
> On Tue, 29 Jul 2003 06:26:18 +0200
> Tomas Szepe <szepe@pinerecords.com> wrote:
>
> > The only aim of the patch is to put most netfilter options
> > in a dedicated submenu so that one can go tweaking the
> > them right where they've enabled netfilter in the first
> > place.
>
> This looks fine to me. Can I get an ACK from the netfilter
> folks?
I also aggree with this change, please apply Tomas' second proposed
patch.
> Thanks.
--
- 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: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-07-30 14:13 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
2003-07-29 4:26 ` Tomas Szepe
2003-07-30 5:38 ` David S. Miller
2003-07-30 14:08 ` Harald Welte [this message]
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=20030730140813.GC4553@sunbeam.de.gnumonks.org \
--to=laforge@netfilter.org \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netfilter-devel@lists.netfilter.org \
--cc=szepe@pinerecords.com \
/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