public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Paul Zimmermann <Paul.Zimmermann@inria.fr>
To: Shuo Wang <wangshuo47@huawei.com>
Cc: libc-alpha@sourceware.org, carlos@redhat.com, hushiyuan@huawei.com
Subject: Re: [PATCH] Fix typo in NEWS file
Date: Tue, 03 Nov 2020 11:40:54 +0100	[thread overview]
Message-ID: <mwk0v23eq1.fsf@tomate.loria.fr> (raw)
In-Reply-To: <7fed9aae-7783-8926-695c-ce25b05cd589@huawei.com> (message from Shuo Wang on Mon, 2 Nov 2020 15:42:13 +0800)

       Dear Shuo,

this patch looks ok to me.

Thanks,
Paul Zimmermann

> From: Shuo Wang <wangshuo47@huawei.com>
> Date: Mon, 2 Nov 2020 15:42:13 +0800
> User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101
>  Thunderbird/78.0.1
> Cc: Hushiyuan <hushiyuan@huawei.com>
> 
> Fix typo in NEWS file
> ---
>   NEWS | 4 ++--
>   1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/NEWS b/NEWS
> index 4307c4b1b0..ff26f6dfa5 100644
> --- a/NEWS
> +++ b/NEWS
> @@ -730,7 +730,7 @@ The following bugs are resolved with this release:
>     [24040] libc: riscv64: unterminated call chain in __thread_start
>     [24047] network: libresolv should use IP_RECVERR/IPV6_RECVERR to avoid
>       long timeouts
> -  [24051] stdio: puts and putchar ouput to _IO_stdout instead of stdout
> +  [24051] stdio: puts and putchar output to _IO_stdout instead of stdout
>     [24059] nss: nss_files: get_next_alias calls fgets_unlocked without
>       checking for NULL.
>     [24114] regex: regexec buffer read overrun in "grep -i
> @@ -1908,7 +1908,7 @@ The following bugs are resolved with this release:
>     [22111] malloc: malloc: per thread cache is not returned when thread 
> exits
>     [22112] localedata: Fix LC_TELEPHONE/LC_NAME for az_AZ
>     [22134] libc: [linux] implement fexecve with execveat
> -  [22142] libc: [powerpc] printf oupts a wrong value of DBL_MAX on 
> ppc64 and
> +  [22142] libc: [powerpc] printf outputs a wrong value of DBL_MAX on 
> ppc64 and
>       ppc64le
>     [22145] libc: ttyname() gives up too early in the face of namespaces
>     [22146] math: C++ build issue with float128 on x86_64
> -- 
> 2.23.0

  reply	other threads:[~2020-11-03 10:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-02  7:42 Shuo Wang
2020-11-03 10:40 ` Paul Zimmermann [this message]
2020-11-03 22:25   ` Joseph Myers
2020-11-02  7:53 Shuo Wang
2020-11-03 12:06 wangshuo (AF)
2020-11-03 12:08 ` Paul Zimmermann
2020-11-05  4:06   ` Carlos O'Donell
2020-11-12  1:37     ` wangshuo (AF)
2020-11-12  6:45       ` Paul Zimmermann
2020-11-17  1:41 Shuo Wang
2020-11-17  8:27 ` Paul Zimmermann
2020-11-28  1:54 Shuo Wang
2020-11-30  9:51 ` Paul Zimmermann
2020-11-30 10:20   ` Siddhesh Poyarekar

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=mwk0v23eq1.fsf@tomate.loria.fr \
    --to=paul.zimmermann@inria.fr \
    --cc=carlos@redhat.com \
    --cc=hushiyuan@huawei.com \
    --cc=libc-alpha@sourceware.org \
    --cc=wangshuo47@huawei.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).