From: Phil Sutter <phil@nwl.cc>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nft,v2] parser_bison: simplify reset syntax
Date: Tue, 14 Mar 2023 18:13:51 +0100 [thread overview]
Message-ID: <ZBCrT68HC5Emwq49@orbyte.nwl.cc> (raw)
In-Reply-To: <20230314165138.828102-1-pablo@netfilter.org>
On Tue, Mar 14, 2023 at 05:51:38PM +0100, Pablo Neira Ayuso wrote:
> Simplify:
>
> *reset rules* *chain* ['family'] 'table' ['chain]'
> to
> *reset rules* ['family'] 'table' 'chain'
>
> *reset rules* *table* ['family'] 'table'
> to
> *reset rules* ['family'] 'table'
>
> *reset counters* ['family'] *table* 'table'
> to
> *reset counters* ['family'] 'table'
>
> *reset quotas* ['family'] *table* 'table'
> to
> *reset quotas* ['family'] 'table'
>
> Previous syntax remains in place for backward compatibility.
>
> Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
> ---
> v2: combine all three lines in manpage
> remove leftover
>
> doc/nft.txt | 8 +++-----
> src/parser_bison.y | 20 ++++++++++++++++++++
> 2 files changed, 23 insertions(+), 5 deletions(-)
>
> diff --git a/doc/nft.txt b/doc/nft.txt
> index 0d60c7520d31..82d3bc4211f1 100644
> --- a/doc/nft.txt
> +++ b/doc/nft.txt
> @@ -490,9 +490,7 @@ RULES
> *replace rule* ['family'] 'table' 'chain' *handle* 'handle' 'statement' ... [*comment* 'comment']
> {*delete* | *reset*} *rule* ['family'] 'table' 'chain' *handle* 'handle'
> *destroy rule* ['family'] 'table' 'chain' *handle* 'handle'
> -*reset rules* ['family']
> -*reset rules* *table* ['family'] 'table'
> -*reset rules* *chain* ['family'] 'table' ['chain']
> +*reset rules* ['family'] ['table'] ['chain']
Sorry for being pedantic, but the above indicates something like 'reset
rules ip mychain' is allowed although it isn't.
prev parent reply other threads:[~2023-03-14 17:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 16:51 [PATCH nft,v2] parser_bison: simplify reset syntax Pablo Neira Ayuso
2023-03-14 17:13 ` Phil Sutter [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=ZBCrT68HC5Emwq49@orbyte.nwl.cc \
--to=phil@nwl.cc \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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