Netdev List
 help / color / mirror / Atom feed
From: esr@thyrsus.com
To: netdev@vger.kernel.org
Subject: Problems in tc-cbq-details.8, tc-cbq.8, tc-mqprio.8, tc-prio.8, tc-htb.8
Date: Tue, 12 Jun 2018 15:16:14 -0400 (EDT)	[thread overview]
Message-ID: <20180612191614.4EFE33A4F6D@snark.thyrsus.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 708 bytes --]

This is automatically generated email about markup problems in a man
page for which you appear to be responsible.  If you are not the right
person or list, please tell me so I can correct my database.

See http://catb.org/~esr/doclifter/bugs.html for details on how and
why these patches were generated.  Feel free to email me with any
questions.  Note: These patches do not change the modification date of
any manual page.  You may wish to do that by hand.

I apologize if this message seems spammy or impersonal. The volume of
markup bugs I am tracking is over five hundred - there is no real
alternative to generating bugmail from a database and template.

--
                             Eric S. Raymond

[-- Attachment #2: Type: text/plain, Size: 379 bytes --]

Problems with tc-mqprio.8:

( ) notation for mandatory parts of command syntax should be { }.

--- tc-mqprio.8-unpatched	2018-05-18 17:15:30.026540775 -0400
+++ tc-mqprio.8	2018-05-18 17:15:41.762461016 -0400
@@ -4,9 +4,9 @@
 .SH SYNOPSIS
 .B tc qdisc ... dev
 dev
-.B  ( parent
+.B  { parent
 classid
-.B | root) [ handle
+.B | root } [ handle
 major:
 .B ] mqprio [ numtc
 tcs

[-- Attachment #3: Type: text/plain, Size: 373 bytes --]

Problems with tc-prio.8:

( ) notation for mandatory parts of command syntax should be { }.

--- tc-prio.8-unpatched	2018-05-18 17:17:17.793808383 -0400
+++ tc-prio.8	2018-05-18 17:17:30.785720088 -0400
@@ -4,9 +4,9 @@
 .SH SYNOPSIS
 .B tc qdisc ... dev
 dev
-.B  ( parent
+.B  { parent
 classid
-.B | root) [ handle
+.B | root } [ handle
 major:
 .B ] prio [ bands
 bands

[-- Attachment #4: Type: text/plain, Size: 374 bytes --]

Problems with tc-htb.8:

( ) notation for mandatory parts of command syntax should be { }.

--- tc-htb.8-unpatched	2018-05-18 17:05:31.142610823 -0400
+++ tc-htb.8	2018-05-18 17:05:42.262535252 -0400
@@ -4,9 +4,9 @@
 .SH SYNOPSIS
 .B tc qdisc ... dev
 dev
-.B  ( parent
+.B  { parent
 classid
-.B | root) [ handle
+.B | root } [ handle
 major:
 .B ] htb [ default
 minor-id

[-- Attachment #5: Type: text/plain, Size: 390 bytes --]

Problems with tc-cbq-details.8:

( ) notation for mandatory parts of command syntax should be { }.

--- tc-cbq-details.8-unpatched	2018-05-18 17:00:55.116486712 -0400
+++ tc-cbq-details.8	2018-05-18 17:01:06.988406029 -0400
@@ -4,9 +4,9 @@
 .SH SYNOPSIS
 .B tc qdisc ... dev
 dev
-.B  ( parent
+.B  { parent
 classid
-.B | root) [ handle
+.B | root} [ handle
 major:
 .B ] cbq avpkt
 bytes

[-- Attachment #6: Type: text/plain, Size: 369 bytes --]

Problems with tc-cbq.8:

( ) notation for mandatory parts of command syntax should be { }.

--- tc-cbq.8-unpatched	2018-05-18 17:03:33.087413133 -0400
+++ tc-cbq.8	2018-05-18 17:03:45.223330656 -0400
@@ -4,9 +4,9 @@
 .SH SYNOPSIS
 .B tc qdisc ... dev
 dev
-.B  ( parent
+.B  { parent
 classid
-.B | root) [ handle
+.B | root } [ handle
 major:
 .B ] cbq [ allot
 bytes

                 reply	other threads:[~2018-06-12 19:16 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20180612191614.4EFE33A4F6D@snark.thyrsus.com \
    --to=esr@thyrsus.com \
    --cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox