netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: luca.boccassi@gmail.com
To: netdev@vger.kernel.org
Subject: [PATCH iproute2 2/2] man: use quote instead of acute accent
Date: Mon, 18 Apr 2022 22:31:28 +0200	[thread overview]
Message-ID: <20220418203128.747915-2-luca.boccassi@gmail.com> (raw)
In-Reply-To: <20220418203128.747915-1-luca.boccassi@gmail.com>

From: Luca Boccassi <bluca@debian.org>

Lintian complains:

I: iproute2: acute-accent-in-manual-page usr/share/man/man8/tc-bpf.8.gz:220

"This manual page uses the \' groff sequence. Usually, the intent to
 generate an apostrophe, but that sequence actually renders as an acute
 accent.
 For an apostrophe or a single closing quote, use plain '. For single
 opening quote, i.e. a straight downward line ' like the one used in
 shell commands, use '\(aq'."

Before:

´s,c t f k,c t f k,c t f k,...´

After:

's,c t f k,c t f k,c t f k,...'

Signed-off-by: Luca Boccassi <bluca@debian.org>
---
Maybe this was the original intention, maybe not, but Lintian nags me, so let's fix it

 man/man8/tc-bpf.8 | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/man/man8/tc-bpf.8 b/man/man8/tc-bpf.8
index e4f68aaa..01230ce6 100644
--- a/man/man8/tc-bpf.8
+++ b/man/man8/tc-bpf.8
@@ -217,7 +217,7 @@ identifiers which would need to reparse packet contents.
 .SS bytecode
 is being used for loading cBPF classifier and actions only. The cBPF bytecode
 is directly passed as a text string in the form of
-.B \'s,c t f k,c t f k,c t f k,...\'
+.B \(aqs,c t f k,c t f k,c t f k,...'
 , where
 .B s
 denotes the number of subsequent 4-tuples. One such 4-tuple consists of
-- 
2.34.1


      reply	other threads:[~2022-04-18 20:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-18 20:31 [PATCH iproute2 1/2] man: 'allow to' -> 'allow one to' luca.boccassi
2022-04-18 20:31 ` luca.boccassi [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=20220418203128.747915-2-luca.boccassi@gmail.com \
    --to=luca.boccassi@gmail.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;
as well as URLs for NNTP newsgroup(s).