From: Alejandro Colomar <alx.manpages@gmail.com>
To: enh <enh@google.com>
Cc: linux-man <linux-man@vger.kernel.org>,
"Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>,
Florian Weimer <fweimer@redhat.com>
Subject: Re: [PATCH] pthread_atfork.3: wfix.
Date: Tue, 26 Jul 2022 13:06:03 +0200 [thread overview]
Message-ID: <7f200367-3751-d110-4c9e-2c0a677eb548@gmail.com> (raw)
In-Reply-To: <CAJgzZoqDAMuk8j-kwzxkKMSbs4z2ZiGzbQuUkrouXitgW+RYmg@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 781 bytes --]
Hi enh,
On 7/25/22 23:00, enh wrote:
> interestingly, i see that commit in the log:
> https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/log/man3/pthread_atfork.3 <https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/log/man3/pthread_atfork.3>
>
> but it doesn't seem to have made it to the web?
> https://man7.org/linux/man-pages/man3/pthread_atfork.3.html
> <https://man7.org/linux/man-pages/man3/pthread_atfork.3.html>
>
> is there a known issue with man7.org <http://man7.org> being out of date?
man7.org shows the latest release. Since we haven't released since
man-pages 5.13, there are many changes in the git repo that aren't found
in that website.
Cheers,
Alex
--
Alejandro Colomar
<http://www.alejandro-colomar.es/>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-07-26 11:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-09 22:27 [PATCH] pthread_atfork.3: wfix enh
2021-11-10 8:11 ` Florian Weimer
2021-11-11 21:49 ` Alejandro Colomar (man-pages)
2021-11-11 22:42 ` enh
2021-11-22 17:02 ` Alejandro Colomar (man-pages)
[not found] ` <CAJgzZoqDAMuk8j-kwzxkKMSbs4z2ZiGzbQuUkrouXitgW+RYmg@mail.gmail.com>
2022-07-26 11:06 ` Alejandro Colomar [this message]
2022-07-26 17:09 ` enh
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=7f200367-3751-d110-4c9e-2c0a677eb548@gmail.com \
--to=alx.manpages@gmail.com \
--cc=enh@google.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