From: Valentin Vidic <vvidic@debian.org>
To: gfs2@lists.linux.dev
Cc: Valentin Vidic <vvidic@debian.org>
Subject: [PATCH] gfs2_edit.8: Fix man page warning
Date: Wed, 26 Feb 2025 21:29:55 +0100 [thread overview]
Message-ID: <20250226202955.1936682-1-vvidic@debian.org> (raw)
W: gfs2-utils: groff-message troff:<standard input>:124: warning: cannot
select font 's' [usr/share/man/man8/gfs2_edit.8.gz:1]
---
gfs2/man/gfs2_edit.8 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gfs2/man/gfs2_edit.8 b/gfs2/man/gfs2_edit.8
index 1a5ccacc..1e9a11c2 100644
--- a/gfs2/man/gfs2_edit.8
+++ b/gfs2/man/gfs2_edit.8
@@ -121,7 +121,7 @@ for example, to artificially change the di_size field for an inode
in order to test fsck.gfs2's ability to detect and fix the problem.
.TP
-\fB-s\fs [\fIstructure\fR | \fIblock\fR]
+\fB-s\fP [\fIstructure\fR | \fIblock\fR]
Specify a starting block for interactive mode. Any of the well-known
locations found in the -p option may be specified. If you want to start
on a particular resource group, specify it in quotes, e.g. -s "rg 3"
--
2.39.5
next reply other threads:[~2025-02-26 20:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-26 20:29 Valentin Vidic [this message]
2025-02-27 11:36 ` [PATCH] gfs2_edit.8: Fix man page warning Andrew Price
2025-02-27 18:45 ` Valentin Vidic
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=20250226202955.1936682-1-vvidic@debian.org \
--to=vvidic@debian.org \
--cc=gfs2@lists.linux.dev \
/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