From: Juan Quintela <quintela@redhat.com>
To: "John Berberian, Jr" <jeb.study@gmail.com>
Cc: "Marc-André Lureau" <marcandre.lureau@gmail.com>,
"Stefan Weil" <sw@weilnetz.de>,
"Daniel P. Berrangé" <berrange@redhat.com>,
qemu-devel@nongnu.org,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [PATCH v2] Fix exec migration on Windows (w32+w64).
Date: Tue, 28 Feb 2023 12:35:02 +0100 [thread overview]
Message-ID: <87lekikopl.fsf@secure.mitica> (raw)
In-Reply-To: <87pm9ukpti.fsf@secure.mitica> (Juan Quintela's message of "Tue, 28 Feb 2023 12:11:05 +0100")
Juan Quintela <quintela@redhat.com> wrote:
> "John Berberian, Jr" <jeb.study@gmail.com> wrote:
>> ping. Is there anything I can do to help this get merged?
>
> Hi
>
> I have to get back from Marc/Daniel before proceed.
>
> You did an answer, but they didn't respond.
>
> What should we do here?
>
> Thanks, Juan.
Reviewed-by: Juan Quintela <quintela@redhat.com>
queued.
Althought I would have preffer to create a
os_get_cmd_path()
in both os-win32.c and os-posix.c, so we don't have the #ifdefs at all.
If you consider doing that, let me know and I will drop this one.
Later, Juan.
next prev parent reply other threads:[~2023-02-28 11:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-16 1:34 [PATCH v2] Fix exec migration on Windows (w32+w64) John Berberian, Jr
2023-01-16 7:17 ` Marc-André Lureau
2023-01-16 9:22 ` Daniel P. Berrangé
2023-01-17 17:07 ` John Berberian, Jr
2023-01-31 4:50 ` John Berberian, Jr.
2023-01-31 10:01 ` Marc-André Lureau
2023-02-18 2:00 ` John Berberian, Jr
2023-02-28 11:11 ` Juan Quintela
2023-02-28 11:24 ` Daniel P. Berrangé
2023-02-28 11:35 ` Juan Quintela [this message]
2023-02-28 11:43 ` Daniel P. Berrangé
2023-02-28 12:51 ` Juan Quintela
2023-02-28 11:22 ` Daniel P. Berrangé
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=87lekikopl.fsf@secure.mitica \
--to=quintela@redhat.com \
--cc=berrange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=jeb.study@gmail.com \
--cc=marcandre.lureau@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=sw@weilnetz.de \
/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.