public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx.manpages@gmail.com>
To: Arjun Shankar <arjun@redhat.com>, linux-man@vger.kernel.org
Cc: Michael Kerrisk <mtk.manpages@gmail.com>,
	Florian Weimer <fweimer@redhat.com>
Subject: Re: [PATCH] pthread_atfork.3: Remove a confusing reference to the current thread
Date: Wed, 13 Apr 2022 20:34:00 +0200	[thread overview]
Message-ID: <9f65abd8-0df3-4c28-7428-21d6fdc59261@gmail.com> (raw)
In-Reply-To: <20220412135520.2388424-1-arjun@redhat.com>


[-- Attachment #1.1: Type: text/plain, Size: 1328 bytes --]

Hi Arjun,

On 4/12/22 15:55, Arjun Shankar wrote:
> The reference to "this thread" in the DESCRIPTION of pthread_atfork(3)
> could be incorrectly interpreted to mean that only handlers registered
> by the thread calling fork(2) are executed.  Therefore, remove the
> reference.
> 
> Signed-off-by: Arjun Shankar <arjun@redhat.com>

I already applied a different patch recently.  See 
<http://www.alejandro-colomar.es/src/alx/linux/man-pages/man-pages.git/commit/man3/pthread_atfork.3?id=f30deb08a9a0db95a3d6b4d00c0927fb43928cc4>.

If you think that can be improved, please send a patch on top of the 
main branch in that repo.

Thanks,

Alex
> ---
>   man3/pthread_atfork.3 | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/man3/pthread_atfork.3 b/man3/pthread_atfork.3
> index b727cb48e..db5e210d4 100644
> --- a/man3/pthread_atfork.3
> +++ b/man3/pthread_atfork.3
> @@ -39,7 +39,7 @@ The
>   .BR pthread_atfork ()
>   function registers fork handlers that are to be executed when
>   .BR fork (2)
> -is called by this thread.
> +is called.
>   The handlers are executed in the context of the thread that calls
>   .BR fork (2).
>   .PP


--
Alejandro Colomar
Linux man-pages comaintainer; http://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

  parent reply	other threads:[~2022-04-13 18:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-12 13:55 [PATCH] pthread_atfork.3: Remove a confusing reference to the current thread Arjun Shankar
2022-04-12 14:31 ` Florian Weimer
2022-04-12 15:10   ` Arjun Shankar
2022-04-13 18:34 ` Alejandro Colomar [this message]
2022-04-13 23:51   ` Arjun Shankar
2022-04-25 20:21     ` 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=9f65abd8-0df3-4c28-7428-21d6fdc59261@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=arjun@redhat.com \
    --cc=fweimer@redhat.com \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    /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