netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: Netfilter Developer Mailing List <netfilter-devel@vger.kernel.org>
Subject: Re: [11/19] libxt_conntrack r0
Date: Sun, 20 Jan 2008 14:33:21 +0100	[thread overview]
Message-ID: <47934DA1.2000502@trash.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0801161451060.4953@fbirervta.pbzchgretzou.qr>

Jan Engelhardt wrote:
> Move libipt_conntrack to libxt_conntrack.
> 
> Signed-off-by: Jan Engelhardt <jengelh@computergmbh.de>
> 
> ---
>  extensions/libipt_conntrack.c                |  514 --------------------------
>  extensions/libipt_conntrack.man              |   49 --
>  extensions/libxt_conntrack.c                 |  517 +++++++++++++++++++++++++++
>  extensions/libxt_conntrack.man               |   71 +++
>  include/linux/netfilter/xt_conntrack.h       |   83 ++++
>  include/linux/netfilter_ipv4/ipt_conntrack.h |   77 ----
>  6 files changed, 671 insertions(+), 640 deletions(-)

Applied, thanks.

  reply	other threads:[~2008-01-20 13:34 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-16 13:46 [0/19] slew of iptables patches Jan Engelhardt
2008-01-16 13:48 ` [01/19] use automake Jan Engelhardt
2008-01-20 13:13   ` Patrick McHardy
2008-01-20 16:51     ` Jan Engelhardt
2008-01-20 16:53       ` Patrick McHardy
2008-01-16 13:48 ` [02/19] strtonum Jan Engelhardt
2008-01-20 13:18   ` Patrick McHardy
2008-01-16 13:49 ` [03/19] common error messages Jan Engelhardt
2008-01-20 13:18   ` Patrick McHardy
2008-01-16 13:49 ` [04/19] libxt_owner Jan Engelhardt
2008-01-20 13:20   ` Patrick McHardy
2008-01-16 13:49 ` [05/19] libxt_tos Jan Engelhardt
2008-01-20 13:21   ` Patrick McHardy
2008-01-16 13:50 ` [06/19] libxt_TOS Jan Engelhardt
2008-01-20 13:24   ` Patrick McHardy
2008-01-16 13:50 ` [07/19] libxt_CONNMARK r1 Jan Engelhardt
2008-01-20 13:27   ` Patrick McHardy
2008-01-16 13:50 ` [08/19] libxt_MARK r2 Jan Engelhardt
2008-01-20 13:30   ` Patrick McHardy
2008-01-16 13:50 ` [09/19] libxt_connmark r1 Jan Engelhardt
2008-01-20 13:31   ` Patrick McHardy
2008-01-16 13:51 ` [10/19] print warning when dlopen fails Jan Engelhardt
2008-01-20 13:32   ` Patrick McHardy
2008-01-16 13:51 ` [11/19] libxt_conntrack r0 Jan Engelhardt
2008-01-20 13:33   ` Patrick McHardy [this message]
2008-01-16 13:51 ` [12/19] bunch o' renames Jan Engelhardt
2008-01-20 13:35   ` Patrick McHardy
2008-01-16 13:52 ` [13/19] rename overlapping function names Jan Engelhardt
2008-01-20 13:37   ` Patrick McHardy
2008-01-16 13:52 ` [14/19] libxt_hashlimit checks Jan Engelhardt
2008-01-20 13:38   ` Patrick McHardy
2008-01-16 13:53 ` [15/19] libxt_mark r1 Jan Engelhardt
2008-01-20 13:40   ` Patrick McHardy
2008-01-16 13:53 ` [16/19] libxt_iprange r0 Jan Engelhardt
2008-01-20 13:42   ` Patrick McHardy
2008-01-20 17:13     ` Jan Engelhardt
2008-01-20 17:19       ` Patrick McHardy
2008-01-20 18:05         ` Jan Engelhardt
2008-01-16 13:54 ` [17/19] libxt_iprange r1 Jan Engelhardt
2008-01-20 13:42   ` Patrick McHardy
2008-01-16 13:54 ` [18/19] libxt_TCPOPTSTRIP Jan Engelhardt
2008-01-17 23:13   ` Sven Schnelle
2008-01-20 13:44     ` Patrick McHardy
2008-01-16 17:57 ` [19/19] xt_conntrack r1 Jan Engelhardt
2008-01-20 13:45   ` 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=47934DA1.2000502@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;
as well as URLs for NNTP newsgroup(s).