From: "Theodore Ts'o" <tytso@mit.edu>
To: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
Cc: "Darrick J. Wong" <djwong@kernel.org>,
Jeremy Bongio <bongiojp@gmail.com>,
linux-ext4@vger.kernel.org, linux-man@vger.kernel.org
Subject: Re: [PATCH v2] Add manpage for get/set fsuuid ioctl for ext4 filesystem.
Date: Fri, 22 Jul 2022 09:55:24 -0400 [thread overview]
Message-ID: <YtqsTM2qXyR+dlz6@mit.edu> (raw)
In-Reply-To: <e1573002-7ea3-2636-b2d2-331767a5622f@gmail.com>
On Fri, Jul 22, 2022 at 12:03:23PM +0200, Alejandro Colomar (man-pages) wrote:
> > SEE ALSO
> > ioctl(2)
> >
> > at the end of an ioctl_XXX manpage like this one.
> >
>
> Okay. Then may I ask for an EXAMPLES section with a program that
> unequivocally shows users how to use it?
I'll note that existing ioctl man pages don't have an explicit
statement that a libc is required --- nor do we do this for open(2),
stat(2), etc. (And that's especially necessary for stat(2), BTW!)
Many of the ioctl man pages (or other system call man pages, for that
matter) also don't have an EXAMPLES section, either.
Perhaps it would be useful to have a discussion over what the
standards are for man pages in section 2, and when we need to state
things that seem to be rather obvious (like "you must have a C
library") and when there should be things like an EXAMPLES section?
Some the suggestions you are making don't seem to be adhered to by
the existing man pages, and more text is not always better.
https://www.npr.org/sections/13.7/2014/02/03/270680304/this-could-have-been-shorter
- Ted
next prev parent reply other threads:[~2022-07-22 13:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-20 23:45 [PATCH v2] Add manpage for get/set fsuuid ioctl for ext4 filesystem Jeremy Bongio
2022-07-21 0:12 ` Darrick J. Wong
2022-07-21 13:04 ` Alejandro Colomar
2022-07-21 18:12 ` Darrick J. Wong
2022-07-22 10:03 ` Alejandro Colomar (man-pages)
2022-07-22 13:55 ` Theodore Ts'o [this message]
2022-07-22 14:32 ` Alejandro Colomar
2022-07-22 17:46 ` Darrick J. Wong
2022-07-22 18:11 ` Alejandro Colomar
2022-07-21 23:13 ` Jeremy Bongio
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=YtqsTM2qXyR+dlz6@mit.edu \
--to=tytso@mit.edu \
--cc=alx.manpages@gmail.com \
--cc=bongiojp@gmail.com \
--cc=djwong@kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-man@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