From: Jan Engelhardt <jengelh@medozas.de>
To: kaber@trash.net
Cc: netfilter-devel@vger.kernel.org
Subject: guided option parser, run 5
Date: Mon, 9 May 2011 11:36:58 +0200 [thread overview]
Message-ID: <1304933832-16412-1-git-send-email-jengelh@medozas.de> (raw)
The following changes since commit edc2b1adf32d2b11e126174f525293b3bca6e7bc:
Merge branch 'opts' of git://dev.medozas.de/iptables (2011-05-09 11:26:32 +0200)
are available in the git repository at:
git://dev.medozas.de/iptables opts
Jan Engelhardt (13):
libxt_tos: add inversion support back again
libxtables: fix assignment in wrong offset (XTTYPE_UINT*RC)
libxt_u32: add missing call to xtables_option_parse
extensions: remove bogus use of XT_GETOPT_TABLEEND
libxt_owner: remove ifdef IPT_COMM_OWNER
libxtables: output name of extension on rev detect failure
extensions: const annotations
libxt_statistic: streamline and document possible placement of negation
libxt_statistic: increase precision on create and dump
libxtables: XTTYPE_DOUBLE support
libxt_statistic: use guided option parser
libxt_IDLETIMER: use guided option parser
libxt_NFLOG: use guided option parser
extensions/libip6t_ipv6header.c | 6 +-
extensions/libip6t_rt.c | 4 +-
extensions/libxt_IDLETIMER.c | 70 +++--------------
extensions/libxt_NFLOG.c | 98 ++++++------------------
extensions/libxt_TCPOPTSTRIP.c | 2 +-
extensions/libxt_dccp.c | 6 +-
extensions/libxt_multiport.c | 10 +-
extensions/libxt_owner.c | 20 -----
extensions/libxt_policy.c | 4 +-
extensions/libxt_rateest.c | 2 +-
extensions/libxt_sctp.c | 6 +-
extensions/libxt_statistic.c | 160 ++++++++++++++++-----------------------
extensions/libxt_statistic.man | 11 +--
extensions/libxt_tcp.c | 6 +-
extensions/libxt_tos.c | 4 +-
extensions/libxt_u32.c | 1 +
extensions/libxt_udp.c | 6 +-
include/xtables.h.in | 5 +-
xtables.c | 4 +-
xtoptions.c | 27 ++++++-
20 files changed, 167 insertions(+), 285 deletions(-)
next reply other threads:[~2011-05-09 9:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-09 9:36 Jan Engelhardt [this message]
2011-05-09 9:36 ` [PATCH 01/13] libxt_tos: add inversion support back again Jan Engelhardt
2011-05-09 9:37 ` [PATCH 02/13] libxtables: fix assignment in wrong offset (XTTYPE_UINT*RC) Jan Engelhardt
2011-05-09 9:37 ` [PATCH 03/13] libxt_u32: add missing call to xtables_option_parse Jan Engelhardt
2011-05-09 9:37 ` [PATCH 04/13] extensions: remove bogus use of XT_GETOPT_TABLEEND Jan Engelhardt
2011-05-09 9:37 ` [PATCH 05/13] libxt_owner: remove ifdef IPT_COMM_OWNER Jan Engelhardt
2011-05-09 9:37 ` [PATCH 06/13] libxtables: output name of extension on rev detect failure Jan Engelhardt
2011-05-09 9:37 ` [PATCH 07/13] extensions: const annotations Jan Engelhardt
2011-05-09 9:37 ` [PATCH 08/13] libxt_statistic: streamline and document possible placement of negation Jan Engelhardt
2011-05-09 9:37 ` [PATCH 09/13] libxt_statistic: increase precision on create and dump Jan Engelhardt
2011-05-09 9:37 ` [PATCH 10/13] libxtables: XTTYPE_DOUBLE support Jan Engelhardt
2011-05-09 9:37 ` [PATCH 11/13] libxt_statistic: use guided option parser Jan Engelhardt
2011-05-09 9:37 ` [PATCH 12/13] libxt_IDLETIMER: " Jan Engelhardt
2011-05-09 9:37 ` [PATCH 13/13] libxt_NFLOG: " Jan Engelhardt
2011-05-09 18:24 ` guided option parser, run 5 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=1304933832-16412-1-git-send-email-jengelh@medozas.de \
--to=jengelh@medozas.de \
--cc=kaber@trash.net \
--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).