From: Matheus Castanho <msc@linux.ibm.com>
To: Florian Weimer <fweimer@redhat.com>,
"Carlos O'Donell via Libc-alpha" <libc-alpha@sourceware.org>
Cc: "Carlos O'Donell" <carlos@redhat.com>, Martin Sebor <msebor@redhat.com>
Subject: Re: [PATCH] mbstowcs: Document, test, and fix null pointer dst semantics.
Date: Mon, 25 May 2020 11:10:42 -0300 [thread overview]
Message-ID: <8a0edaad-a511-2847-23c3-dcc220b8a8ef@linux.ibm.com> (raw)
In-Reply-To: <87wo53292m.fsf@oldenburg2.str.redhat.com>
On 5/22/20 2:06 PM, Florian Weimer wrote:
> * Carlos O'Donell via Libc-alpha:
>
>> On 5/22/20 12:15 PM, Matheus Castanho wrote:
>>> Just tested the patch (on ppc64le) and the problem I reported on the
>>> Bugzilla issue has been solved.
>>>
>>> Thanks for working on the fix.
>>
>> Matheus thanks for testing!
>>
>> Can you please provide the URL to the bug?
>
> It's a comment on bug 25219:
>
> <https://sourceware.org/bugzilla/show_bug.cgi?id=25219#c3>
That's the one. Thanks, Florian.
I just commented on the issue since it was related to that topic.
--
Matheus Castanho
next prev parent reply other threads:[~2020-05-25 14:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-22 2:15 Carlos O'Donell
2020-05-22 11:25 ` Florian Weimer
2020-06-01 15:50 ` [PATCH v2] mbstowcs: Document, test, and fix null pointer dst semantics (Bug 25219) Carlos O'Donell
2020-06-01 16:17 ` Florian Weimer
2020-06-01 16:28 ` Carlos O'Donell
2020-06-01 16:35 ` Florian Weimer
2020-06-01 16:57 ` [PATCH v3] " Carlos O'Donell
2020-06-01 17:07 ` Florian Weimer
2020-06-01 17:11 ` Carlos O'Donell
2020-05-22 15:56 ` [PATCH] mbstowcs: Document, test, and fix null pointer dst semantics Martin Sebor
2020-05-22 16:15 ` Matheus Castanho
2020-05-22 16:35 ` Carlos O'Donell
2020-05-22 17:06 ` Florian Weimer
2020-05-25 14:10 ` Matheus Castanho [this message]
2020-06-01 13:40 ` Matheus Castanho
2020-06-01 15:11 ` Carlos O'Donell
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=8a0edaad-a511-2847-23c3-dcc220b8a8ef@linux.ibm.com \
--to=msc@linux.ibm.com \
--cc=carlos@redhat.com \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=msebor@redhat.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).