From: Rusty Russell <rusty@rustcorp.com.au>
To: Harald Welte <laforge@netfilter.org>
Cc: netdev@oss.sgi.com, Netfilter Core Team <coreteam@netfilter.org>,
Netfilter development mailing list
<netfilter-devel@lists.netfilter.org>,
lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>,
Adrian Bunk <bunk@stusta.de>
Subject: Re: [netfilter-core] [2.6 patch] net/ipv4/netfilter/: misc possible cleanups
Date: Thu, 16 Dec 2004 12:40:48 +1100 [thread overview]
Message-ID: <1103161248.2200.7.camel@localhost.localdomain> (raw)
In-Reply-To: <20041215090322.GA2862@sunbeam.de.gnumonks.org>
On Wed, 2004-12-15 at 10:03 +0100, Harald Welte wrote:
> On Wed, Dec 15, 2004 at 02:19:31AM +0100, Adrian Bunk wrote:
> > The patch below contains the following possible cleanups:
...
> As you might be aware, netfilter/iptables has an enormously large
> codebase (I'd say even larger than what is in the tree) in the so-called
> patch-o-matic subsystem. The abovementioned exports facilitate those
> modulse, and A certain amount of those new modules (especially the ones
> requiring the functions above) are scheduled for mainline inclusion over
> the next couple of months.
True, but some of these cleanups are genuine. Deleting code also
increases the coverage of the testsuite: I've put this in my patch set
and will merge them in pieces. At the rate I work, those that are
needed in the next few months won't be deleted. If patches are not due
to be merged in that timeframe, it'd be nice if they contained the
exports etc. that they need rather than relying on long-term unused
features of the tree.
Cheers,
Rusty.
--
A bad analogy is like a leaky screwdriver -- Richard Braakman
prev parent reply other threads:[~2004-12-16 1:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-15 1:19 [2.6 patch] net/ipv4/netfilter/: misc possible cleanups Adrian Bunk
2004-12-15 9:03 ` [netfilter-core] " Harald Welte
2004-12-16 1:40 ` Rusty Russell [this message]
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=1103161248.2200.7.camel@localhost.localdomain \
--to=rusty@rustcorp.com.au \
--cc=bunk@stusta.de \
--cc=coreteam@netfilter.org \
--cc=laforge@netfilter.org \
--cc=linux-kernel@vger.kernel.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).