From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Peng Haitao <penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
carlos-v2tUB8YBRSi3e3T8WW9gsA@public.gmane.org,
aoliva-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] strcpy.3: ATTRIBUTES: Note functions that are thread-safe
Date: Sun, 02 Mar 2014 07:20:37 +0100 [thread overview]
Message-ID: <5312CDB5.1070500@gmail.com> (raw)
In-Reply-To: <1393550095-14200-1-git-send-email-penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
Applied. Thanks, Haitao.
Cheers,
Michael
On 02/28/2014 02:14 AM, Peng Haitao wrote:
> The functions strcpy() and strncpy() are thread safe.
>
> Signed-off-by: Peng Haitao <penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
> ---
> man3/strcpy.3 | 9 ++++++++-
> 1 file changed, 8 insertions(+), 1 deletion(-)
>
> diff --git a/man3/strcpy.3 b/man3/strcpy.3
> index 675b72e..da027c3 100644
> --- a/man3/strcpy.3
> +++ b/man3/strcpy.3
> @@ -32,7 +32,7 @@
> .\" 2007-06-15, Marc Boyer <marc.boyer-oUYRw6/Rnm9Wj0EZb7rXcA@public.gmane.org> + mtk
> .\" Improve discussion of strncpy().
> .\"
> -.TH STRCPY 3 2012-07-19 "GNU" "Linux Programmer's Manual"
> +.TH STRCPY 3 2014-02-28 "GNU" "Linux Programmer's Manual"
> .SH NAME
> strcpy, strncpy \- copy a string
> .SH SYNOPSIS
> @@ -113,6 +113,13 @@ and
> functions return a pointer to
> the destination string
> .IR dest .
> +.SH ATTRIBUTES
> +.SS Multithreading (see pthreads(7))
> +The
> +.BR strcpy ()
> +and
> +.BR strncpy ()
> +functions are thread-safe.
> .SH CONFORMING TO
> SVr4, 4.3BSD, C89, C99.
> .SH NOTES
>
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
--
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:[~2014-03-02 6:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-28 1:14 [PATCH] strcpy.3: ATTRIBUTES: Note functions that are thread-safe Peng Haitao
[not found] ` <1393550095-14200-1-git-send-email-penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2014-03-02 6:20 ` Michael Kerrisk (man-pages) [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=5312CDB5.1070500@gmail.com \
--to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@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=penght-BthXqXjhjHXQFUHtdCDX3A@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.