Linux Netfilter development
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH 03/10] Remove support for compilation of conditional extensions
Date: Tue, 15 Apr 2008 13:41:23 +0200	[thread overview]
Message-ID: <48049463.2080005@trash.net> (raw)
In-Reply-To: <bfc44342f0ecd2278412e98409f6d98ae307eb69.1208255176.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_condition.c          |   94 -----
>  extensions/libipt_condition.man        |    4 -
>  include/linux/netfilter_ipv4/ip_set.h  |  498 ++++++++++++++++++++++++
>  include/linux/netfilter_ipv4/ipt_set.h |   21 +
>  10 files changed, 522 insertions(+), 233 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_condition.c
>  delete mode 100644 extensions/libipt_condition.man
>  create mode 100644 include/linux/netfilter_ipv4/ip_set.h
>  create mode 100644 include/linux/netfilter_ipv4/ipt_set.h

Applied.

  reply	other threads:[~2008-04-15 11:41 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-15 10:33 iptables updates Jan Engelhardt
2008-04-15 10:33 ` [PATCH 01/10] Resolve warnings on 64-bit compile Jan Engelhardt
2008-04-15 10:33   ` [PATCH 02/10] Wrap dlopen code into NO_SHARED_LIBS Jan Engelhardt
2008-04-15 11:38     ` Patrick McHardy
2008-04-15 10:33   ` [PATCH 03/10] Remove support for compilation of conditional extensions Jan Engelhardt
2008-04-15 11:41     ` Patrick McHardy [this message]
2008-04-15 10:33   ` [PATCH 04/10] Resolve libipt_set warnings Jan Engelhardt
2008-04-15 11:42     ` Patrick McHardy
2008-04-15 10:33   ` [PATCH 05/10] Update documentation about building the package Jan Engelhardt
2008-04-15 11:43     ` Patrick McHardy
2008-04-15 10:33   ` [PATCH 06/10] configure.ac: AC_SUBST must be separate Jan Engelhardt
2008-04-15 11:43     ` Patrick McHardy
2008-04-15 10:33   ` [PATCH 07/10] Dynamically create xtables.h.in with version Jan Engelhardt
2008-04-15 11:44     ` Patrick McHardy
2008-04-15 10:33   ` [PATCH 09/10] Move libipt_recent to libxt_recent Jan Engelhardt
2008-04-15 10:33   ` [PATCH 10/10] libxt_recent: add missing --rsource,--rdest options to manpage Jan Engelhardt
2008-04-15 11:38   ` [PATCH 01/10] Resolve warnings on 64-bit compile Patrick McHardy
2008-04-15 11:19 ` [PATCH 11] configure.ac: remove already-defined variables Jan Engelhardt
2008-04-15 11:48   ` Patrick McHardy
     [not found] ` <7c7d0eb43b7b4ca3711ae0dbe17ae7ef66fb02f8.1208255176.git.jengelh@computergmbh.de>
2008-04-15 11:47   ` [PATCH 08/10] Remove old functions, constants Patrick McHardy
2008-04-15 11:49     ` Jan Engelhardt
2008-04-15 11:50       ` 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=48049463.2080005@trash.net \
    --to=kaber@trash.net \
    --cc=jengelh@computergmbh.de \
    --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