From: Phil Sutter <phil@nwl.cc>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org, Quentin Deslandes <qde@naccy.de>
Subject: Re: [nft PATCH v2 1/2] doc: nft.8: Two minor synopsis fixups
Date: Fri, 12 Apr 2024 13:27:25 +0200 [thread overview]
Message-ID: <ZhkanVAuKQmdolkd@orbyte.nwl.cc> (raw)
In-Reply-To: <20240326132651.21274-2-phil@nwl.cc>
On Tue, Mar 26, 2024 at 02:26:50PM +0100, Phil Sutter wrote:
> The curly braces in 'add table' are to be put literally, so need to be
> bold. Also, they are optional unless either one (or both) of 'comment'
> and 'flags' are specified.
>
> The 'add chain' synopsis contained a stray tick, messing up the
> following markup.
>
> Fixes: 7fd67ce121f86 ("doc: fix synopsis of named counter, quota and ct {helper,timeout,expect}")
> Signed-off-by: Phil Sutter <phil@nwl.cc>
Patch applied, will respin the second one.
next prev parent reply other threads:[~2024-04-12 11:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-26 13:26 [nft PATCH v2 0/2] Add support for table's persist flag Phil Sutter
2024-03-26 13:26 ` [nft PATCH v2 1/2] doc: nft.8: Two minor synopsis fixups Phil Sutter
2024-04-12 11:27 ` Phil Sutter [this message]
2024-03-26 13:26 ` [nft PATCH v2 2/2] Add support for table's persist flag Phil Sutter
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=ZhkanVAuKQmdolkd@orbyte.nwl.cc \
--to=phil@nwl.cc \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=qde@naccy.de \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).