From: Laurent Vivier <laurent@vivier.eu>
To: Antonio Ospite <antonio.ospite@collabora.com>,
Antonio Ospite <ao2@ao2.it>,
qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [Qemu-devel] [PATCH v3 0/2] configure: disallow spaces and colons in source path and build path
Date: Wed, 26 Jun 2019 17:50:14 +0200 [thread overview]
Message-ID: <4d4588e3-b804-7774-756a-3c8092fe732f@vivier.eu> (raw)
In-Reply-To: <adce6062-9289-afe8-b26a-949144700656@collabora.com>
Le 26/06/2019 à 17:16, Antonio Ospite a écrit :
> On 26/05/19 16:47, Antonio Ospite wrote:
>> Hi,
>>
>> Here is a v3 set to address
>> https://bugs.launchpad.net/qemu/+bug/1817345
>>
>> CCing Laurent Vivier as the patch is going through the trivial-patches
>> branch.
>>
>
> Ping.
>
> I cannot see this in the trivial-patches repository nor in mainline qemu.
>
I missed it because you didn't cc: qemu-trivial ML (I use this list to
pick up the patches).
I'm going to add them to the next pull request.
Thanks,
Laurent
next prev parent reply other threads:[~2019-06-26 15:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-26 14:47 [Qemu-devel] [PATCH v3 0/2] configure: disallow spaces and colons in source path and build path Antonio Ospite
2019-05-26 14:47 ` [Qemu-devel] [PATCH v3 1/2] configure: set source_path only once and make its definition more robust Antonio Ospite
2019-06-26 15:56 ` Laurent Vivier
2019-05-26 14:47 ` [Qemu-devel] [PATCH v3 2/2] configure: disallow spaces and colons in source path and build path Antonio Ospite
2019-06-26 15:56 ` Laurent Vivier
2019-06-26 15:16 ` [Qemu-devel] [PATCH v3 0/2] " Antonio Ospite
2019-06-26 15:50 ` Laurent Vivier [this message]
2019-06-26 15:54 ` Antonio Ospite
2019-06-26 15:52 ` Eric Blake
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=4d4588e3-b804-7774-756a-3c8092fe732f@vivier.eu \
--to=laurent@vivier.eu \
--cc=antonio.ospite@collabora.com \
--cc=ao2@ao2.it \
--cc=peter.maydell@linaro.org \
--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 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).