From: Patrick McHardy <kaber@trash.net>
To: Yasuyuki KOZAKAI <yasuyuki.kozakai@toshiba.co.jp>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: [SUBPATCH IPTABLES 0/43]: Unification of ip[6]tables matches/targets #3
Date: Fri, 20 Jul 2007 13:27:20 +0200 [thread overview]
Message-ID: <46A09C18.60608@trash.net> (raw)
In-Reply-To: <200707201110.l6KBAsq5001901@toshiba.co.jp>
Yasuyuki KOZAKAI wrote:
> I've updated libxt_tcp and libxt_multiport according to comments from Jan.
> This time I post only updated patches and the undeliverd patch in previous
> time due to large patch.
>
> [09-1/43] Fixed warning on compilation of iptables matches/targets
> [09-2/43] Fixed warning on compilation of ip6tables matches/targets
> [10/43] fixed warning on compilation, part 2
> [17/43] Use unified API in multiport match.
> [18/43] Split ipt_multport into family dependent parts and others
> [19/43] Moves libipt_multiport.c to libxt_multiport.c
> [20/43] Unifies libip[6]t_multiport.c into libipxt_multiport.c
> [28/43] Unifies libip[6]t_tcp.c into libxt_tcp.c
>
Looks good to me.
> From: Yasuyuki KOZAKAI <yasuyuki.kozakai@toshiba.co.jp>
>
>
>> Well, I found missing FIN in text of help() in libipt_tcp.c then also
>> fixed. New release is necessary again ? grrr.. If so, I'll change version
>> in Makefile, and apply xtables patches to main trunk.
>>
>
> If no one wants new release again before commiting thse patches,
> I'll commit them into main trunk without changing version in Makefile
> next week (maybe Tuesday).
Great, thanks a lot Yasuyuki. I'm really looking forward to seeing
this in SVN.
next parent reply other threads:[~2007-07-20 11:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200707201110.l6KBAsq5001901@toshiba.co.jp>
2007-07-20 11:27 ` Patrick McHardy [this message]
2007-07-17 3:44 [PATCH 28/43] Unifies libip[6]t_tcp.c into libxt_tcp.c Yasuyuki KOZAKAI
2007-07-20 11:10 ` [SUBPATCH IPTABLES 0/43]: Unification of ip[6]tables matches/targets #3 Yasuyuki KOZAKAI
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=46A09C18.60608@trash.net \
--to=kaber@trash.net \
--cc=netfilter-devel@lists.netfilter.org \
--cc=yasuyuki.kozakai@toshiba.co.jp \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.