From: "wangshuo (AF)" <wangshuo47@huawei.com>
To: "libc-alpha@sourceware.org" <libc-alpha@sourceware.org>,
Paul Zimmermann <Paul.Zimmermann@inria.fr>
Cc: Carlos O'Donell <carlos@redhat.com>, Hushiyuan <hushiyuan@huawei.com>
Subject: RE: [PATCH] Fix typo in NEWS file
Date: Thu, 12 Nov 2020 01:37:29 +0000 [thread overview]
Message-ID: <c4c6b171f8744a938b16d3bdc5e83910@huawei.com> (raw)
In-Reply-To: <19fab423-063a-d3ec-40f1-be29c2c697ce@redhat.com>
Dear Paul,
I was wondering if these two changes will be merged?
Thank you,
Shuo
-----Original Message-----
From: Carlos O'Donell [mailto:carlos@redhat.com]
Sent: Thursday, November 5, 2020 12:07 PM
To: Paul Zimmermann <Paul.Zimmermann@inria.fr>; wangshuo (AF) <wangshuo47@huawei.com>
Cc: libc-alpha@sourceware.org; Hushiyuan <hushiyuan@huawei.com>
Subject: Re: [PATCH] Fix typo in NEWS file
On 11/3/20 7:08 AM, Paul Zimmermann wrote:
> your second patch (https://sourceware.org/pipermail/libc-alpha/2020-November/119285.html) is fine to me too.
Paul,
Are you able to commit these changes yourself?
I'm happy to see anyone from the community commit obvious changes like this so long as the bug title was fixed in bugzilla.
Joseph's suggestion to re-run the script is certainly a gold-star solution, but just committing the fixes is fine by me.
--
Cheers,
Carlos.
next prev parent reply other threads:[~2020-11-12 1:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
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) [this message]
2020-11-12 6:45 ` Paul Zimmermann
-- strict thread matches above, loose matches on Subject: below --
2020-11-28 1:54 Shuo Wang
2020-11-30 9:51 ` Paul Zimmermann
2020-11-30 10:20 ` Siddhesh Poyarekar
2020-11-17 1:41 Shuo Wang
2020-11-17 8:27 ` Paul Zimmermann
2020-11-02 7:53 Shuo Wang
2020-11-02 7:42 Shuo Wang
2020-11-03 10:40 ` Paul Zimmermann
2020-11-03 22:25 ` Joseph Myers
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=c4c6b171f8744a938b16d3bdc5e83910@huawei.com \
--to=wangshuo47@huawei.com \
--cc=Paul.Zimmermann@inria.fr \
--cc=carlos@redhat.com \
--cc=hushiyuan@huawei.com \
--cc=libc-alpha@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).