From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: iptables: spaces, spaces.
Date: Wed, 16 Feb 2011 14:23:48 +0100 [thread overview]
Message-ID: <4D5BCFE4.8060701@trash.net> (raw)
In-Reply-To: <1297822737-11204-1-git-send-email-jengelh@medozas.de>
On 16.02.2011 03:18, Jan Engelhardt wrote:
> The following changes since commit af3d73ec867debb5e38c6c6fde66f05093714fec:
>
> iptables: fix segfault target option parsing (2011-02-11 01:46:45 +0100)
>
> are available in the git repository at:
> git://dev.medozas.de/iptables master
>
> Jan Engelhardt (3):
> ip6tables: spacing fixes for -o argument
> libxt_devgroup: option whitespace update following v1.4.10-49-g7386635
> extensions: fix indent of vtable
Pulled, thanks Jan.
prev parent reply other threads:[~2011-02-16 13:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-16 2:18 iptables: spaces, spaces Jan Engelhardt
2011-02-16 2:18 ` [PATCH 1/3] ip6tables: spacing fixes for -o argument Jan Engelhardt
2011-02-16 2:18 ` [PATCH 2/3] libxt_devgroup: option whitespace update following v1.4.10-49-g7386635 Jan Engelhardt
2011-02-16 2:18 ` [PATCH 3/3] extensions: fix indent of vtable Jan Engelhardt
2011-02-16 13:23 ` 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=4D5BCFE4.8060701@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).