public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: Salvatore Bonaccorso <carnil@debian.org>
Cc: linux-man@vger.kernel.org
Subject: Re: proc.5: Still refers to "described in more detail below" for splitted out manpages
Date: Fri, 12 Apr 2024 19:47:07 +0200	[thread overview]
Message-ID: <ZhlzmymKd3XBq9Yh@debian> (raw)
In-Reply-To: <Zhlth9wCHbxoNkMi@eldamar.lan>

[-- Attachment #1: Type: text/plain, Size: 845 bytes --]

Hi Salvatore,

On Fri, Apr 12, 2024 at 07:21:11PM +0200, Salvatore Bonaccorso wrote:
> 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_"?

Thanks for catching this.  Yeah, something like that makes sense.

You could add to the commit message:

Fixes: 92cdcec79df0 ("proc.5: Clean up after making sashimi of this page")

Have a lovely day!
Alex

> 
> Regards,
> Salvatore
> 

-- 
<https://www.alejandro-colomar.es/>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2024-04-12 17:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-12 17:21 proc.5: Still refers to "described in more detail below" for splitted out manpages Salvatore Bonaccorso
2024-04-12 17:47 ` Alejandro Colomar [this message]
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=ZhlzmymKd3XBq9Yh@debian \
    --to=alx@kernel.org \
    --cc=carnil@debian.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