From: Ma Shimiao <mashimiao.fnst-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
To: "Stéphane Aulery" <saulery-GANU6spQydw@public.gmane.org>
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Michael Kerrisk
<mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
621057-forwarded-61a8vm9lEZVf4u+23C9RwQ@public.gmane.org
Subject: Re: manpages-dev: please note thread safeness of %m in vfprintf(3)
Date: Mon, 9 Mar 2015 16:23:49 +0800 [thread overview]
Message-ID: <54FD5895.8090805@cn.fujitsu.com> (raw)
In-Reply-To: <20150309074735.GA1144-GANU6spQydw@public.gmane.org>
Hi Stéphane,
On 03/09/2015 03:47 PM, Stéphane Aulery wrote:
> Hello Ma Shimiao,
>
> Le lundi 09 mars 2015 à 02:20:07, Ma Shimiao a écrit :
>>
>> On 03/07/2015 06:38 PM, Stéphane Aulery wrote:
>>>
>>> A Debian user has applied to mention that strerror_r(3) is thread safe.
>>>
>>>> Frome Martin Godisch <martin-AOktpf5JBruELgA04lAiVw@public.gmane.org>, Wed, 6 Apr 2011 09:30:30 +0200
>>>>
>>>> Please add a note to vfprintf(3) telling users that the %m conversion
>>>> specifier is thread safe.
>>
>> I'm not sure why he need a note to indicate that the %m conversion specifier
>> is thread safe.
>> From our research and glibc's document, vfprintf(3) is thread safe except when users pass float formatting,
>> custom formatting or single quota may cause locale dependency problem.
>> And I'm going to add thread safety information of vfprintf() into printf.3.
>> If there is something special about %m, we'd like to know.
>> And I'm willing to add it.
>
> I will send you answer to Martin Godisch, but I don't think there is something
> special. I will wait your patch before closing this bug.
OK. I will send my patch as soon as possible.
Best regards,
>
> Thanks.
>
> Regards,
>
--
Ma Shimiao
Development Dept.I
Nanjing Fujitsu Nanda Software Tech. Co., Ltd.(FNST)
--
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:[~2015-03-09 8:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-07 10:38 manpages-dev: please note thread safeness of %m in vfprintf(3) Stéphane Aulery
[not found] ` <20150307103821.GA2043-GANU6spQydw@public.gmane.org>
2015-03-09 6:20 ` Ma Shimiao
[not found] ` <54FD3B97.5050400-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2015-03-09 7:47 ` Stéphane Aulery
[not found] ` <20150309074735.GA1144-GANU6spQydw@public.gmane.org>
2015-03-09 8:23 ` Ma Shimiao [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=54FD5895.8090805@cn.fujitsu.com \
--to=mashimiao.fnst-bthxqxjhjhxqfuhtdcdx3a@public.gmane.org \
--cc=621057-forwarded-61a8vm9lEZVf4u+23C9RwQ@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=saulery-GANU6spQydw@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).