From: Salvatore Bonaccorso <carnil@debian.org>
To: Alejandro Colomar <alx@kernel.org>
Cc: linux-man@vger.kernel.org
Subject: proc.5: Still refers to "described in more detail below" for splitted out manpages
Date: Fri, 12 Apr 2024 19:21:11 +0200 [thread overview]
Message-ID: <Zhlth9wCHbxoNkMi@eldamar.lan> (raw)
Hi Alejandro
Back in August 2023, various parts were split out of proc(5) into
separate manpage. What seems to have remained from the split is the
mentioning:
[...]
178 .P
179 All of the above are described in more detail below.
[...]
I'm not sure what you would like to prefer, so I have no explict patch
here. But maybe this can be reworded to "All of the above are desribed
in sepate manpages prefixes with proc_"?
Regards,
Salvatore
next reply other threads:[~2024-04-12 17:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-12 17:21 Salvatore Bonaccorso [this message]
2024-04-12 17:47 ` proc.5: Still refers to "described in more detail below" for splitted out manpages Alejandro Colomar
2024-04-12 18:37 ` Salvatore Bonaccorso
2024-04-12 19:51 ` Alejandro Colomar
2024-04-12 20:04 ` Salvatore Bonaccorso
2024-04-12 20:57 ` Alejandro Colomar
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=Zhlth9wCHbxoNkMi@eldamar.lan \
--to=carnil@debian.org \
--cc=alx@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).