All of lore.kernel.org
 help / color / mirror / Atom feed
From: Duncan Roe <duncan_roe@optusnet.com.au>
To: Netfilter Development <netfilter-devel@vger.kernel.org>
Subject: man page nft.8 add chain synopsis
Date: Fri, 6 Oct 2017 16:08:38 +1100	[thread overview]
Message-ID: <20171006050838.GA9956@dimstar.local.net> (raw)

Hi,

The man page says this:

> {add | create} chain [family] table chain [ { {type} {hook} [device] {priority} } [policy] ]

But I suggest it should say this:

> {add | create} chain [family] table chain [ { {type} {hook} [device] {priority ;} [policy ;] } ]

i.e. the policy tuple should be inside the braces along with type, hook, device
& priority. Also the device & priority tuples each need to be followed by a
semicolon.

** Is the above change correct?

* Assuming it is correct, the patch below makes the change. Can someone pick it
  up from here or should I submit a bug report?

Cheers ... Duncan.

---

diff --git a/doc/nft.xml b/doc/nft.xml
index c0f42dd..80ffcd7 100644
--- a/doc/nft.xml
+++ b/doc/nft.xml
@@ -664,9 +664,9 @@ filter input iif $int_ifs accept
						<arg choice="req"><replaceable>type</replaceable></arg>
						<arg choice="req"><replaceable>hook</replaceable></arg>
						<arg choice="opt"><replaceable>device</replaceable></arg>
-						<arg choice="req"><replaceable>priority</replaceable></arg>
+						<arg choice="req"><replaceable>priority</replaceable> ;</arg>
+						<arg choice="opt"><replaceable>policy</replaceable> ;</arg>
					</arg>
-					<arg choice="opt"><replaceable>policy</replaceable></arg>
				</arg>
			</cmdsynopsis>
			<cmdsynopsis>

             reply	other threads:[~2017-10-06  5:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-06  5:08 Duncan Roe [this message]
2017-10-06 12:52 ` man page nft.8 add chain synopsis 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=20171006050838.GA9956@dimstar.local.net \
    --to=duncan_roe@optusnet.com.au \
    --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.