From: Yubin Ruan <ablacktshirt@gmail.com>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: linux-man@vger.kernel.org, libc-alpha@sourceware.org
Subject: Re: [PATCTH 0/2] pthread_mutexattr_setrobust() and pthread_mutex_consistent()
Date: Tue, 22 Aug 2017 02:19:00 -0000 [thread overview]
Message-ID: <CAJYFCiPM6Hy1cPF2mUBu5bVqxNX+5kvKnJZLhYzMMwuMiHCKeg@mail.gmail.com> (raw)
In-Reply-To: <36ab9ec0-b496-c007-c12f-065fd618e7fd@gmail.com>
2017-08-22 8:33 GMT+08:00 Michael Kerrisk (man-pages) <mtk.manpages@gmail.com>:
> Hello Yubin
>
> On 08/20/2017 11:42 AM, Yubin Ruan wrote:
>> Hi Michael,
>> This patch series introduce three pthread functions for linux-man:
>> * pthread_mutexattr_setrobust()
>> * pthread_mutexattr_getrobust()
>> * pthread_mutex_consistent()
>>
>> I put pthread_mutexattr_setrobust() and pthread_mutexattr_getrobust()
>> altogether since they are related.
>>
>> I obtain my information about these functions mainly from reading the
>> glibc source code and do some testing. There might be some mistake,
>> but they are mostly correct (95% or so).
>>
>> Following this email would be those man pages in plain text and nroff
>> format. I have tested those nroff file on my Linux box using man, and
>> it look pretty well. Please point out if there are any mistake in
>> formatting.
>
> Thanks for the drafts. Could I ask you to review the man-pages(7)
> page. There's a number of details described in that page
> which should be fixed in the drafts. Also, please try rendering
> your pages with "man -l <page>". This will show problems with
> the example code. See the chown(2) man page example for
> the required escape sequences for "\n" and the single quote.
No problem. I would fix the formatting issues.
Yubin
next prev parent reply other threads:[~2017-08-22 2:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-20 9:43 Yubin Ruan
2017-08-21 2:25 ` Yubin Ruan
2017-08-21 2:31 ` Yubin Ruan
2017-08-22 0:33 ` Michael Kerrisk (man-pages)
2017-08-22 2:19 ` Yubin Ruan [this message]
2017-08-26 14:10 ` Yubin Ruan
2017-09-11 1:50 ` Yubin Ruan
2017-09-11 20:35 ` Michael Kerrisk (man-pages)
2017-09-12 12:41 ` Michael Kerrisk (man-pages)
2017-09-13 1:39 ` Yubin Ruan
2017-09-13 4:09 ` Yubin Ruan
2017-09-13 12:28 ` Michael Kerrisk (man-pages)
2017-09-15 1:34 ` Yubin Ruan
2017-09-13 15:00 ` Michael Kerrisk (man-opages)
2017-09-15 2:49 ` Yubin Ruan
2017-09-15 7:53 ` 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=CAJYFCiPM6Hy1cPF2mUBu5bVqxNX+5kvKnJZLhYzMMwuMiHCKeg@mail.gmail.com \
--to=ablacktshirt@gmail.com \
--cc=libc-alpha@sourceware.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).