From: Peng Haitao <penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
To: Carlos O'Donell <carlos-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: Michael Kerrisk
<mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Alexandre Oliva <aoliva-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
GNU C Library
<libc-alpha-9JcytcrH/bA+uJoB2kUjGw@public.gmane.org>,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Documenting MT-safe vs. MT-unsafe.
Date: Thu, 25 Jul 2013 11:13:52 +0800 [thread overview]
Message-ID: <51F097F0.2010007@cn.fujitsu.com> (raw)
In-Reply-To: <51F08029.1000403-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
On 07/25/2013 09:32 AM, Carlos O'Donell wrote:
> At present I am a little worried that glibc is going
> to document what we want to be true e.g. MT-unsafe,
> but that the linux kernel man pages project is going
> to document what is actually implemented e.g. MT-safe.
> This may lead users to believe functions are safe
> when they are not guaranteed to be so.
>
> The other problem is that the two documents might
> diverge and this information is very important.
>
> What can we do to keep the two documents in sync?
>
At present, when make the patch, I will look up Alex's result
(branch lxoliva/thread-safety-docs).
If thread-safety level is the same with Alex or POSIX,
I will send the patch. otherwise, the patch will be put off.
> When Alex completes his project we'll have MT-safety
> data (with a series of exceptions) for almost all
> of the glibc functions. Could we use that data to
> drive the generation of the attributes in the
> linux kernel man pages?
>
Maybe this will wait for a long time:(
--
Best Regards,
Peng
> Comments?
>
> Cheers,
> Carlos.
>
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2013-07-25 3:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-25 1:32 Documenting MT-safe vs. MT-unsafe Carlos O'Donell
[not found] ` <51F08029.1000403-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-07-25 3:13 ` Peng Haitao [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=51F097F0.2010007@cn.fujitsu.com \
--to=penght-bthxqxjhjhxqfuhtdcdx3a@public.gmane.org \
--cc=aoliva-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=carlos-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=libc-alpha-9JcytcrH/bA+uJoB2kUjGw@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
/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 NNTP newsgroup(s).