From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Zeng Linggang <zenglg.jy-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH ] ATTRIBUTES: new correct versions
Date: Sat, 11 Apr 2015 08:53:16 +0200 [thread overview]
Message-ID: <5528C4DC.6000006@gmail.com> (raw)
In-Reply-To: <1428461788-7518-1-git-send-email-zenglg.jy-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
On 04/08/2015 04:56 AM, Zeng Linggang wrote:
> Hi,
>
> This patch-set is the new correct versions for previous patches from me.
>
> 1. Fix an English grammar mistake in the title: "those" should be "that".
> 2. Quote the glibc markings in the commit message.
>
> ps:
> Please *ignore* all patches before this patch-set sent by me.
> Include the child thread about below subject:
> [PATCH v2] getutent.3: ATTRIBUTES: Note functions those aren't thread-safe
> [PATCH] ctime.3: ATTRIBUTES: Note functions thoes aren't thread-safe
> [PATCH] asprintf.3: ATTRIBUTES: Note functions those are thread-safe
> [PATCH] getutent.3: ATTRIBUTES: Note functions those aren't thread-safe
Thanks, Zeng. Perfect! I have applied all of the following, sent by you
on 8 April:
asprintf.3: ATTRIBUTES: Note functions that are thread-safe
ctime.3: ATTRIBUTES: Note functions that aren't thread-safe
gethostbyname.3: ATTRIBUTES: Note functions that aren't thread-safe
getnetent.3: ATTRIBUTES: Note functions that aren't thread-safe
get_nprocs_conf.3: ATTRIBUTES: Note functions that are thread-safe
getutent.3: ATTRIBUTES: Note functions that aren't thread-safe
mbsnrtowcs.3: ATTRIBUTES: Note function that isn't thread-safe
mbsrtowcs.3: ATTRIBUTES: Note function that isn't thread-safe
perror.3: ATTRIBUTES: Note function that is thread-safe
printf.3: ATTRIBUTES: Note functions that are thread-safe
scandir.3: ATTRIBUTES: Note functions that are thread-safe
scanf.3: ATTRIBUTES: Note functions that are thread-safe
unlocked_stdio.3: ATTRIBUTES: Note functions that aren't thread-safe
wcrtomb.3: ATTRIBUTES: Note function that isn't thread-safe
wcsnrtombs.3: ATTRIBUTES: Note function that isn't thread-safe
wcsrtombs.3: ATTRIBUTES: Note function that isn't thread-safe
wprintf.3: ATTRIBUTES: Note functions that are thread-safe
I believe that is everything. Please let me know if there is
something from you that I should still apply.
Cheers,
Michael
--
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
next prev parent reply other threads:[~2015-04-11 6:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-08 2:56 [PATCH ] ATTRIBUTES: new correct versions Zeng Linggang
[not found] ` <1428461788-7518-1-git-send-email-zenglg.jy-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2015-04-08 2:56 ` [PATCH] asprintf.3: ATTRIBUTES: Note functions that are thread-safe Zeng Linggang
2015-04-08 2:56 ` [PATCH] ctime.3: ATTRIBUTES: Note functions that aren't thread-safe Zeng Linggang
2015-04-08 2:56 ` [PATCH] gethostbyname.3: " Zeng Linggang
2015-04-08 2:56 ` [PATCH] getnetent.3: " Zeng Linggang
2015-04-08 2:56 ` [PATCH] get_nprocs_conf.3: ATTRIBUTES: Note functions that are thread-safe Zeng Linggang
2015-04-08 2:56 ` [PATCH] getutent.3: ATTRIBUTES: Note functions that aren't thread-safe Zeng Linggang
2015-04-08 2:56 ` [PATCH] mbsnrtowcs.3: ATTRIBUTES: Note function that isn't thread-safe Zeng Linggang
2015-04-08 2:56 ` [PATCH] mbsrtowcs.3: " Zeng Linggang
2015-04-08 2:56 ` [PATCH] perror.3: ATTRIBUTES: Note function that is thread-safe Zeng Linggang
2015-04-08 2:56 ` [PATCH] printf.3: ATTRIBUTES: Note functions that are thread-safe Zeng Linggang
2015-04-08 2:56 ` [PATCH] scandir.3: " Zeng Linggang
2015-04-08 2:56 ` [PATCH] scanf.3: " Zeng Linggang
2015-04-08 2:56 ` [PATCH] unlocked_stdio.3: ATTRIBUTES: Note functions that aren't thread-safe Zeng Linggang
2015-04-08 2:56 ` [PATCH] wcrtomb.3: ATTRIBUTES: Note function that isn't thread-safe Zeng Linggang
2015-04-08 2:56 ` [PATCH] wcsnrtombs.3: " Zeng Linggang
2015-04-08 2:56 ` [PATCH] wcsrtombs.3: " Zeng Linggang
2015-04-08 2:56 ` [PATCH] wprintf.3: ATTRIBUTES: Note functions that are thread-safe Zeng Linggang
2015-04-11 6:53 ` Michael Kerrisk (man-pages) [this message]
[not found] ` <5528C4DC.6000006-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-04-13 1:32 ` [PATCH ] ATTRIBUTES: new correct versions Zeng Linggang
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=5528C4DC.6000006@gmail.com \
--to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=zenglg.jy-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.