From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: netfilter-devel@vger.kernel.org,
Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Subject: Re: [PATCH 7/8] Remove support for compilation of conditional extensions
Date: Mon, 14 Apr 2008 08:46:48 +0200 [thread overview]
Message-ID: <4802FDD8.301@trash.net> (raw)
In-Reply-To: <2b2e38a1bfc0069830bd5cfe535fa52b7ee8a0da.1208075035.git.jengelh@computergmbh.de>
Jan Engelhardt wrote:
> ---
> extensions/.condition-test | 4 -
> extensions/.condition-test6 | 4 -
> extensions/.set-test | 4 -
> extensions/GNUmakefile.in | 27 +----
> extensions/libip6t_condition.c | 95 ----------------
> extensions/libip6t_condition.man | 4 -
> extensions/libipt_SET.c | 174 ------------------------------
> extensions/libipt_SET.man | 16 ---
> extensions/libipt_condition.c | 94 ----------------
> extensions/libipt_condition.man | 4 -
> extensions/libipt_set.c | 161 ---------------------------
> extensions/libipt_set.h | 104 ------------------
> extensions/libipt_set.man | 17 ---
> 13 files changed, 3 insertions(+), 705 deletions(-)
> delete mode 100755 extensions/.condition-test
> delete mode 100755 extensions/.condition-test6
> delete mode 100755 extensions/.set-test
> delete mode 100644 extensions/libip6t_condition.c
> delete mode 100644 extensions/libip6t_condition.man
> delete mode 100644 extensions/libipt_SET.c
> delete mode 100644 extensions/libipt_SET.man
> delete mode 100644 extensions/libipt_condition.c
> delete mode 100644 extensions/libipt_condition.man
> delete mode 100644 extensions/libipt_set.c
> delete mode 100644 extensions/libipt_set.h
> delete mode 100644 extensions/libipt_set.man
Was there some resolution on the discussion that this
is the way to go? I mainly would like to see an ACK
from Jozsef for this change before applying it.
next prev parent reply other threads:[~2008-04-14 6:46 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-13 8:25 A few more iptables patches Jan Engelhardt
2008-04-13 8:25 ` [PATCH 1/8] Import iptables-apply Jan Engelhardt
2008-04-13 8:25 ` [PATCH 2/8] Add all necessary header files - compilation fix for various cases Jan Engelhardt
2008-04-13 8:29 ` Patrick McHardy
2008-04-14 6:40 ` Patrick McHardy
2008-04-13 8:25 ` [PATCH 3/8] Install libiptc header files because xtables.h depends on it Jan Engelhardt
2008-04-14 6:41 ` Patrick McHardy
2008-04-13 8:25 ` [PATCH 4/8] iptables: use C99 lists for struct options Jan Engelhardt
2008-04-14 6:42 ` Patrick McHardy
2008-04-13 8:25 ` [PATCH 5/8] Combine ipt and ip6t manpages Jan Engelhardt
2008-04-14 6:44 ` Patrick McHardy
2008-04-14 6:55 ` Jan Engelhardt
2008-04-14 7:00 ` Patrick McHardy
2008-04-13 8:25 ` [PATCH 6/8] RATEEST: add manpage Jan Engelhardt
2008-04-14 6:45 ` Patrick McHardy
2008-04-13 8:25 ` [PATCH 7/8] Remove support for compilation of conditional extensions Jan Engelhardt
2008-04-14 6:46 ` Patrick McHardy [this message]
2008-04-14 6:53 ` Jan Engelhardt
2008-04-14 6:56 ` Patrick McHardy
2008-04-14 13:14 ` Jan Engelhardt
2008-04-14 13:20 ` Jozsef Kadlecsik
2008-04-14 15:31 ` Patrick McHardy
2008-04-13 8:25 ` [PATCH 8/8] Implement AF_UNSPEC as a wildcard for extensions Jan Engelhardt
2008-04-14 6:47 ` Patrick McHardy
2008-04-14 6:38 ` [PATCH 1/8] Import iptables-apply Patrick McHardy
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=4802FDD8.301@trash.net \
--to=kaber@trash.net \
--cc=jengelh@computergmbh.de \
--cc=kadlec@blackhole.kfki.hu \
--cc=netfilter-devel@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