From: Florian Westphal <fw@strlen.de>
To: Arturo Borrero Gonzalez <arturo@debian.org>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [nft,RFC] rule: introduce new option to print set elements per line
Date: Tue, 25 Apr 2017 11:20:10 +0200 [thread overview]
Message-ID: <20170425092010.GA21171@breakpoint.cc> (raw)
In-Reply-To: <149277062417.14594.14270713486442491994.stgit@nfdev2.cica.es>
Arturo Borrero Gonzalez <arturo@debian.org> wrote:
> Add a new option to nft to print set elements per line instead
> of all in a single line.
> This is useful when printing a ruleset with very big sets.
>
> The new option is -t/--elements.
>
> Annonymous sets/maps/concats are not affected by this. The default
> behaviour is not changed.
Nice patch, thanks Arturo!
Why make this an option in first place?
> % nft list ruleset -t -nn
> table ip t {
> set s {
> type inet_service
> elements = { 1,
> 2,
> 3,
> 4,
> 12345 }
> }
How hard would it be to make it so that this is still
printed in single line (enough space left)?
> set s2 {
> type ipv4_addr . inet_service
> elements = { 1.1.1.1 . 22,
> 1.1.1.1 . 222,
> 1.1.1.1 . 2222,
> 2.1.1.1 . 22222 }
> }
But not this?
Printing all addresses in a single line is unreadable, it seems
strange to have an option to make it nice and then make 'unreadable'
the default :)
next prev parent reply other threads:[~2017-04-25 9:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-21 10:30 [nft RFC PATCH] rule: introduce new option to print set elements per line Arturo Borrero Gonzalez
2017-04-25 9:20 ` Florian Westphal [this message]
2017-04-25 9:22 ` Pablo Neira Ayuso
2017-04-25 9:35 ` Arturo Borrero Gonzalez
2017-04-25 9:44 ` Florian Westphal
2017-04-25 10:15 ` Pablo Neira Ayuso
2017-04-25 10:15 ` Pablo Neira Ayuso
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=20170425092010.GA21171@breakpoint.cc \
--to=fw@strlen.de \
--cc=arturo@debian.org \
--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.