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>
Cc: linux-man@vger.kernel.org,
	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: Mon, 25 Apr 2022 22:21:32 +0200	[thread overview]
Message-ID: <6dbbc686-73ed-2ce7-9d3b-2896b4c7cba8@gmail.com> (raw)
In-Reply-To: <CAG_osaYFb6mfX8x0SqgHpoj3GL8oyNZmFYzDiG696cH1_bTbcQ@mail.gmail.com>

Hi Arjun,

On 4/14/22 01:51, Arjun Shankar wrote:
> Hi Alex,
> 
>> 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>.
> 
> I wasn't aware of this repository and therefore missed the change.
> I'll keep it in mind. >
>> If you think that can be improved, please send a patch on top of the
>> main branch in that repo.
> 
> The commit you mentioned looks good to me. Apologies for the noise and
> thanks for looking into this.

No problem.  It's not noise, IMO :-)
It's always nice to have more wording options to consider.

Cheers,

Alex

      reply	other threads:[~2022-04-25 20:21 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
2022-04-13 23:51   ` Arjun Shankar
2022-04-25 20:21     ` Alejandro Colomar [this message]

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=6dbbc686-73ed-2ce7-9d3b-2896b4c7cba8@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