From: Jon LaBadie <jonfu@jgcomp.com>
To: netdev@vger.kernel.org
Subject: ip manpage comments
Date: Sat, 26 Nov 2016 21:49:32 -0500 [thread overview]
Message-ID: <20161127024932.GA9954@cyber.jgcomp.com> (raw)
Though not new to *nix, I am new to using the ip(8) command.
Thus some of my historical assumptions about ip may be wrong.
It seems that an inclusive manpage for the ip command was
broken up into a shorter ip(8) manpage and 15 or more
ip-<subcommand>(8) manpages. I'm basing this assumption
on long, inclusive manpages on https://linux.die.net/man/8/ip
and CentOS 6 while CentOS 7 and Fedora 24 each have the
sub-divided style.
I won't debate the wisdom of this subdivision, only comment
on how it was done.
The ip(8) manpage make no mention of additional subordinate
documents. The listing of the additional documents in the
See Also section is insufficient. This section is typically
used to mention related commands and other sources of reference
materials such as info docs, wikis, blogs, or mailing lists.
When one does investigate one of the subordinate manpages,
they do not state that they document subcommands of the
ip command. In fact, on the ip-address(8) manpage it says
The `ip address command' ... (quotes added)
My first thought was "typo", this is the manpage about the
"ip-address" command. Of course there is no ip-address command.
But "ip address" is not a command either, it is the "ip" command
with an argument.
There are several commands that have broken their manpage into
several manpages. Two which come to mind are zsh(1) and perl(1).
The authors of those pages clearly state on the primary manpage
that this is an overview page and give clear pointers to the
additional manpages as well as additional documentation. I would
recommend reorganizing the ip(8) manpage in a similar fashion.
Thank you for consideration of my opinion and for the development
of an awesome tool.
Jon
--
Jon H. LaBadie jonfu@jgcomp.com
next reply other threads:[~2016-11-27 3:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-27 2:49 Jon LaBadie [this message]
2016-11-28 10:53 ` ip manpage comments Phil Sutter
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=20161127024932.GA9954@cyber.jgcomp.com \
--to=jonfu@jgcomp.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).