From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: iptables: headers, chain length
Date: Thu, 24 Jun 2010 17:01:21 +0200 [thread overview]
Message-ID: <4C237341.4070004@trash.net> (raw)
In-Reply-To: <1277367245-14961-1-git-send-email-jengelh@medozas.de>
Jan Engelhardt wrote:
> The following changes since commit d40f1628c3717daebc437a398a285e371b5b6f7f:
>
> libxt_set: new revision added (2010-06-16 12:45:33 +0200)
>
> are available in the git repository at:
> git://dev.medozas.de/iptables master
>
> Jan Engelhardt (3):
> includes: sync header files from Linux 2.6.35-rc1
> xtables: another try at chain name length checking
> xtables: remove xtables_set_revision function
Pulled, thanks Jan.
prev parent reply other threads:[~2010-06-24 15:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-24 8:14 iptables: headers, chain length Jan Engelhardt
2010-06-24 8:14 ` [PATCH 1/3] includes: sync header files from Linux 2.6.35-rc1 Jan Engelhardt
2010-06-24 8:14 ` [PATCH 2/3] xtables: another try at chain name length checking Jan Engelhardt
2010-06-24 8:14 ` [PATCH 3/3] xtables: remove xtables_set_revision function Jan Engelhardt
2010-06-24 15:01 ` 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=4C237341.4070004@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 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).