From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: iptables: misc option edits
Date: Wed, 23 Feb 2011 17:40:34 +0100 [thread overview]
Message-ID: <4D653882.7070501@trash.net> (raw)
In-Reply-To: <1298142259-11213-1-git-send-email-jengelh@medozas.de>
Am 19.02.2011 20:04, schrieb Jan Engelhardt:
> Please review! (And if ok, merge.)
>
> ===
>
> The following changes since commit 87dc7c4c842deb1e2e3d38089ffcad9f238d98de:
>
> xtables: use strspn() to check if string needs to be quoted (2011-02-17 11:57:19 +0100)
>
> are available in the git repository at:
> git://dev.medozas.de/iptables master
>
> Jan Engelhardt (8):
> doc: fix wrong sentence about negation in xt_limit
> doc: fix misspelling of "field"
> extensions: remove redundant init functions
> Remove unused CVS expanded keywords
> libip6t_dst: remove unimplemented --dst-not-strict
> libip6t_hbh: remove unimplemented --hbh-not-strict
> extensions: add missing checks for specific flags
> libipt_ECN: set proper option flags
>
Looks good, pulled, thanks Jan.
prev parent reply other threads:[~2011-02-23 16:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-19 19:04 iptables: misc option edits Jan Engelhardt
2011-02-19 19:04 ` [PATCH 1/8] doc: fix wrong sentence about negation in xt_limit Jan Engelhardt
2011-02-19 19:04 ` [PATCH 2/8] doc: fix misspelling of "field" Jan Engelhardt
2011-02-19 19:04 ` [PATCH 3/8] extensions: remove redundant init functions Jan Engelhardt
2011-02-19 19:04 ` [PATCH 4/8] Remove unused CVS expanded keywords Jan Engelhardt
2011-02-19 19:04 ` [PATCH 5/8] libip6t_dst: remove unimplemented --dst-not-strict Jan Engelhardt
2011-02-19 19:04 ` [PATCH 6/8] libip6t_hbh: remove unimplemented --hbh-not-strict Jan Engelhardt
2011-02-19 19:04 ` [PATCH 7/8] extensions: add missing checks for specific flags Jan Engelhardt
2011-02-19 19:04 ` [PATCH 8/8] libipt_ECN: set proper option flags Jan Engelhardt
2011-02-23 16:40 ` Patrick McHardy [this message]
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=4D653882.7070501@trash.net \
--to=kaber@trash.net \
--cc=jengelh@medozas.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 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.