From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Akihiko Odaki <akihiko.odaki@daynix.com>
Cc: Jason Wang <jasowang@redhat.com>,
qemu-devel@nongnu.org, devel@daynix.com
Subject: Re: [PATCH v2 1/2] glib-compat: Define g_spawn_check_wait_status()
Date: Mon, 6 Jan 2025 09:22:41 +0000 [thread overview]
Message-ID: <Z3ug4WRFoXufrBbj@redhat.com> (raw)
In-Reply-To: <20250104-glib-v2-1-12013f3e5782@daynix.com>
On Sat, Jan 04, 2025 at 05:04:07PM +0900, Akihiko Odaki wrote:
> g_spawn_check_exit_status() is renamed to g_spawn_check_wait_status()
> in 2.70.
>
> Signed-off-by: Akihiko Odaki <akihiko.odaki@daynix.com>
> ---
> include/glib-compat.h | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/include/glib-compat.h b/include/glib-compat.h
> index 86be439ba0ef..0bddb327bd5d 100644
> --- a/include/glib-compat.h
> +++ b/include/glib-compat.h
> @@ -68,6 +68,8 @@
> * without generating warnings.
> */
>
> +#define g_spawn_check_wait_status g_spawn_check_exit_status
This needs to be conditionalized on !GLIB_CHECK_VERSION(2, 70, 0)
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2025-01-06 9:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-04 8:04 [PATCH v2 0/2] tap: Use g_spawn_sync() and g_spawn_check_wait_status() Akihiko Odaki
2025-01-04 8:04 ` [PATCH v2 1/2] glib-compat: Define g_spawn_check_wait_status() Akihiko Odaki
2025-01-06 9:22 ` Daniel P. Berrangé [this message]
2025-01-04 8:04 ` [PATCH v2 2/2] tap: Use g_spawn_sync() and g_spawn_check_wait_status() Akihiko Odaki
2025-01-06 9:34 ` Daniel P. Berrangé
2025-01-15 6:04 ` Akihiko Odaki
2025-01-15 10:38 ` Daniel P. Berrangé
2025-01-07 1:45 ` Lei Yang
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=Z3ug4WRFoXufrBbj@redhat.com \
--to=berrange@redhat.com \
--cc=akihiko.odaki@daynix.com \
--cc=devel@daynix.com \
--cc=jasowang@redhat.com \
--cc=qemu-devel@nongnu.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.