From: Mike Frysinger <vapier@gentoo.org>
To: Karel Zak <kzak@redhat.com>
Cc: util-linux@vger.kernel.org
Subject: Re: [PATCH] mount(8): drop redundant filesystem-specific sections
Date: Wed, 24 Jan 2018 23:24:26 -0500 [thread overview]
Message-ID: <20180125042426.GE1718@vapier> (raw)
In-Reply-To: <20180122090923.io62zeuwnv25iw7p@ws.net.home>
[-- Attachment #1: Type: text/plain, Size: 1210 bytes --]
On 22 Jan 2018 10:09, Karel Zak wrote:
> On Fri, Jan 19, 2018 at 01:45:20PM -0500, Mike Frysinger wrote:
> > Add a new section to the top of the filesystem-specific chapter to point
> > people generally to the filesystem-specific man pages. This way we can
> > delete all the redundant subsections that say the same thing.
>
> Well, the subsections also provides the name of the package where is FS
> specific man page :-)
>
> > -.SS "Mount options for xfs"
> > -See the options section of the
> > -.BR xfs (5)
> > -man page (the xfsprogs package must be installed).
>
> It's probably not so important (and I have no strong opinion about
> it), but I can imagine that for end-users it's useful. Maybe we can
> add to the man page a small table with FS name, man page and package
> name:
>
> xfs xfs(5) xfsprogs
> ext4 ext4(5) e2fsprogs
> cifs mount.cifs(8) cifs-utils
> ...
>
> or is it overkill?
the only reason i hesitated to try and do that was due to cross-distro
package naming idiosyncrasies. but i guess if we refer to the upstream
project using the name they choose, the rest can be an exercise for the
user ?
-mike
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-01-25 4:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-19 18:45 [PATCH] mount(8): drop redundant filesystem-specific sections Mike Frysinger
2018-01-22 9:01 ` Karel Zak
2018-01-25 4:23 ` Mike Frysinger
2018-01-22 9:09 ` Karel Zak
2018-01-25 4:24 ` Mike Frysinger [this message]
2018-01-30 10:35 ` Karel Zak
2018-01-24 13:25 ` 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=20180125042426.GE1718@vapier \
--to=vapier@gentoo.org \
--cc=kzak@redhat.com \
--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 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.