From: Johannes Unglert <unglert@b1-systems.de>
To: util-linux@vger.kernel.org
Subject: Improvement suggestion for mkfs.8 manpage
Date: Wed, 6 Feb 2019 16:43:14 +0100 [thread overview]
Message-ID: <8cac72fd-8116-53e9-1a7f-5c22377dce04@b1-systems.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 567 bytes --]
Hello,
i stumbled upon a minor spelling error in the mkfs.8 manpage.
It´s an capitalization error for the verbose option.
Please see attached diff for more information.
How should i handle this? What´s the desired procedure?
Do you want me to create a pull-request?
with best regards
Johannes Unglert
--
Johannes Unglert
Auszubildender Fachinformatik - AE
Tel.: +49 1512 2088159
Mail: unglert@b1-systems.de
B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt, HRB 3537
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: mkfs.8.patch --]
[-- Type: text/x-patch; name="mkfs.8.patch", Size: 767 bytes --]
*** util-linux/disk-utils/mkfs.8 2019-02-06 16:16:12.585415680 +0100
--- util-linux/disk-utils/mkfs.8.new 2019-02-06 16:16:25.693415630 +0100
***************
*** 43,49 ****
.I fs-options
Filesystem-specific options to be passed to the real filesystem builder.
.TP
! .BR \-V , " \-\-verbose"
Produce verbose output, including all filesystem-specific commands
that are executed.
Specifying this option more than once inhibits execution of any
--- 43,49 ----
.I fs-options
Filesystem-specific options to be passed to the real filesystem builder.
.TP
! .BR \-v , " \-\-verbose"
Produce verbose output, including all filesystem-specific commands
that are executed.
Specifying this option more than once inhibits execution of any
next reply other threads:[~2019-02-06 15:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-06 15:43 Johannes Unglert [this message]
2019-02-07 16:13 ` Improvement suggestion for mkfs.8 manpage Theodore Y. Ts'o
2019-02-08 9:47 ` Johannes Unglert
2019-02-08 15:20 ` Theodore Y. Ts'o
2019-02-11 9:41 ` Karel Zak
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=8cac72fd-8116-53e9-1a7f-5c22377dce04@b1-systems.de \
--to=unglert@b1-systems.de \
--cc=util-linux@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).