From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Florian Westphal <fw@strlen.de>
Cc: nft.ogxzcrqhuhgchbvxcs4j7wws@qmail.sunbirdgrove.com,
netfilter@vger.kernel.org,
netfilter-devel <netfilter-devel@vger.kernel.org>
Subject: Re: nft list sets changed behavior
Date: Sun, 18 Jun 2023 17:21:38 +0200 [thread overview]
Message-ID: <ZI8hArHRm2ke+Awz@calendula> (raw)
In-Reply-To: <20230618133509.GA869@breakpoint.cc>
On Sun, Jun 18, 2023 at 03:35:09PM +0200, Florian Westphal wrote:
> moving to nf-devel
>
> nft.ogxzcrqhuhgchbvxcs4j7wws@qmail.sunbirdgrove.com <nft.ogxzcrqhuhgchbvxcs4j7wws@qmail.sunbirdgrove.com> wrote:
[...]
> > > > After updating to Debian 12 my tools relying on 'nft -j list sets' fail.
> > > > It now does not include the elements in those lists like it did on 11.
>
> I see three possible solutions:
> 1 - accept the breakage.
> 2 - repair the inconsistency so we get 1.0.0 and
> earlier behaviour back.
> 3 - make "list sets" *always* include set elements,
> unless --terse was given.
>
> Thoughts? I'd go with 3, I dislike the
> different behaviour that 2) implies and we already
> have --terse, we just need to make use of it here.
I'd go with 3 too, so --terse is honored.
next prev parent reply other threads:[~2023-06-18 15:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-18 0:42 nft list sets changed behavior nft.ogxzcrqhuhgchbvxcs4j7wws
2023-06-18 11:22 ` Kerin Millar
2023-06-18 12:12 ` nft.ogxzcrqhuhgchbvxcs4j7wws
2023-06-18 13:35 ` Florian Westphal
2023-06-18 13:44 ` nft.ogxzcrqhuhgchbvxcs4j7wws
2023-06-18 15:21 ` Pablo Neira Ayuso [this message]
2023-06-18 16:05 ` Kerin Millar
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=ZI8hArHRm2ke+Awz@calendula \
--to=pablo@netfilter.org \
--cc=fw@strlen.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=netfilter@vger.kernel.org \
--cc=nft.ogxzcrqhuhgchbvxcs4j7wws@qmail.sunbirdgrove.com \
/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.