From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Markus Wichmann <nullplan@gmx.net>, musl@lists.openwall.com
Cc: mtk.manpages@gmail.com
Subject: Re: [musl] Simple question regarding read-write locks precedence
Date: Tue, 31 Mar 2020 21:02:24 +0200 [thread overview]
Message-ID: <e9258e85-b2cf-c2f6-719c-654c800021cd@gmail.com> (raw)
In-Reply-To: <20200331183839.GB2683@voyager>
On 3/31/20 8:38 PM, Markus Wichmann wrote:
> On Tue, Mar 31, 2020 at 01:37:24PM -0400, Rich Felker wrote:
>> I think that's pretty clearly just a mistake in the man page that
>> should be reported. CC'ing.
>>
>> Rich
>
> Well, nevermind. I just realized that I only checked my local manpages,
> which are version 4.15, whereas the online version is 5.05, and the
> online release no longer has a Bugs section, instead inlining the
> information into the Description section.
Yes. See https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/commit/?id=0d255e74c098dd2ad420367503398ad7f8f82024
> The only mention of writer
> recursion in the online version is in the description of
> PTHREAD_RWLOCK_PREFER_WRITER_NP. That also probably means to say reader.
So, is there still something you think needs fixing in the page?
Thanks,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
next prev parent reply other threads:[~2020-03-31 19:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-31 15:05 Koen Vandeputte
2020-03-31 15:09 ` Rich Felker
2020-03-31 15:21 ` Koen Vandeputte
2020-03-31 15:26 ` Rich Felker
2020-03-31 17:21 ` Markus Wichmann
2020-03-31 17:37 ` Rich Felker
2020-03-31 18:38 ` Markus Wichmann
2020-03-31 19:02 ` Michael Kerrisk (man-pages) [this message]
2020-03-31 19:45 ` Markus Wichmann
2020-03-31 20:15 ` Michael Kerrisk (man-pages)
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=e9258e85-b2cf-c2f6-719c-654c800021cd@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=musl@lists.openwall.com \
--cc=nullplan@gmx.net \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).