From: Kostiantyn Kostiuk <kkostiuk@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: "Markus Armbruster" <armbru@redhat.com>,
qemu-devel@nongnu.org, "Yan Vugenfirer" <yvugenfi@redhat.com>,
"Daniel Berrangé" <berrange@redhat.com>
Subject: Re: [PATCH] util: win32: Write hex value when can't get error message
Date: Mon, 28 Jul 2025 12:58:34 +0300 [thread overview]
Message-ID: <CAPMcbCrhuuEbSUTk7a_h9bc-a70JekF682ozzYS=8MeUyf3uWA@mail.gmail.com> (raw)
In-Reply-To: <44ca54d5-1292-4388-9436-dca2b6e7e97f@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 689 bytes --]
Based on the following part from the new docs
* If a human readable message cannot be found for the given @error, an empty
* string is returned.
Do you have any objections to this patch?
Best Regards,
Konstantin Kostiuk.
On Mon, Jul 28, 2025 at 12:48 PM Philippe Mathieu-Daudé <philmd@linaro.org>
wrote:
> On 25/7/25 11:59, Kostiantyn Kostiuk wrote:
> > Issue reported to GLib https://gitlab.gnome.org/GNOME/glib/-/issues/3740
> > <https://gitlab.gnome.org/GNOME/glib/-/issues/3740>
> > PR with fix https://gitlab.gnome.org/GNOME/glib/-/merge_requests/4716
> > <https://gitlab.gnome.org/GNOME/glib/-/merge_requests/4716>
>
> Even already merged, thank you!
>
>
[-- Attachment #2: Type: text/html, Size: 2566 bytes --]
next prev parent reply other threads:[~2025-07-28 10:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-17 14:59 [PATCH] util: win32: Write hex value when can't get error message Kostiantyn Kostiuk
2025-07-17 15:28 ` Yan Vugenfirer
2025-07-19 6:27 ` Markus Armbruster
2025-07-21 7:07 ` Kostiantyn Kostiuk
2025-07-21 9:22 ` Markus Armbruster
2025-07-21 10:12 ` Kostiantyn Kostiuk
2025-07-21 11:23 ` Yan Vugenfirer
2025-07-21 11:53 ` Philippe Mathieu-Daudé
2025-07-25 9:59 ` Kostiantyn Kostiuk
2025-07-28 9:47 ` Philippe Mathieu-Daudé
2025-07-28 9:58 ` Kostiantyn Kostiuk [this message]
2025-07-28 11:12 ` Markus Armbruster
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='CAPMcbCrhuuEbSUTk7a_h9bc-a70JekF682ozzYS=8MeUyf3uWA@mail.gmail.com' \
--to=kkostiuk@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=yvugenfi@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 NNTP newsgroup(s).