From: Patrick McHardy <kaber@trash.net>
To: Ana Rey <anarey@gmail.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [nft PATCH] expression: Fix inconsistent output in set
Date: Sat, 12 Apr 2014 11:49:24 +0200 [thread overview]
Message-ID: <20140412094924.GA2682@macbook.localnet> (raw)
In-Reply-To: <1daccfe0798bd032f1770b0ae7888a88db46f3f6.1397204678.git.anarey@gmail.com>
On Fri, Apr 11, 2014 at 10:26:46AM +0200, Ana Rey wrote:
> Add a whitespace between the last element in a set and the close braces.
>
> Old output set:
>
> set set-test {
> type ipv4_address
> elements = { 192.168.1.44, 192.168.2.4}
> }
>
> New output set:
> set set-test {
> type ipv4_address
> elements = { 192.168.1.44, 192.168.2.4 }
> }
>
That's actually deliberate. A space is always added before a set member, but never
after.
prev parent reply other threads:[~2014-04-12 9:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-11 8:26 [nft PATCH] expression: Fix inconsistent output in set Ana Rey
2014-04-12 9:49 ` 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=20140412094924.GA2682@macbook.localnet \
--to=kaber@trash.net \
--cc=anarey@gmail.com \
--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).