From: Peng Haitao <penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
To: Michael Kerrisk <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: carlos-v2tUB8YBRSi3e3T8WW9gsA@public.gmane.org,
aoliva-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] getlogin.3: ATTRIBUTES: Note function that is not thread-safe
Date: Fri, 24 May 2013 08:51:58 +0800 [thread overview]
Message-ID: <519EB9AE.6010902@cn.fujitsu.com> (raw)
In-Reply-To: <519DF98D.2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
On 05/23/2013 07:12 PM, Michael Kerrisk wrote:
>> +The
>> +.BR cuserid ()
>> +function is thread-safe with exceptions.
>
> Peng,
>
> I think it would be good to describe the exceptions here. Okay?
> Could you adjust and resent.
>
OK, thanks.
--
Best Regards,
Peng
> Thanks,
>
> Michael
>
>
>> .SH CONFORMING TO
>> .BR getlogin ()
>> and
>>
>
> --
> 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
>
--
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-05-24 0:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-23 8:44 [PATCH] getlogin.3: ATTRIBUTES: Note function that is not thread-safe Peng Haitao
[not found] ` <1369298684-892-1-git-send-email-penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2013-05-23 11:12 ` Michael Kerrisk
[not found] ` <519DF98D.2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-05-24 0:51 ` 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=519EB9AE.6010902@cn.fujitsu.com \
--to=penght-bthxqxjhjhxqfuhtdcdx3a@public.gmane.org \
--cc=aoliva-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=carlos-v2tUB8YBRSi3e3T8WW9gsA@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.