From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: "Peter Maydell" <peter.maydell@linaro.org>,
"Daniel P. Berrangé" <berrange@redhat.com>
Cc: "Jan Kiszka" <jan.kiszka@siemens.com>,
"Samuel Thibault" <samuel.thibault@ens-lyon.org>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>
Subject: Re: [Qemu-devel] [PULL 0/2] slirp: move slirp as git submodule project
Date: Wed, 8 May 2019 07:48:18 +0200 [thread overview]
Message-ID: <f6bb0085-34a3-7b65-da19-b78cd71e9630@redhat.com> (raw)
In-Reply-To: <CAFEAcA9NM8c0bX+D-VFOvO7iOWjcyv1U=F5K5810mHRb-zgDZw@mail.gmail.com>
On 5/7/19 7:01 PM, Peter Maydell wrote:
> On Tue, 7 May 2019 at 15:19, Daniel P. Berrangé <berrange@redhat.com> wrote:
>> On Tue, May 07, 2019 at 09:11:09AM -0500, Eric Blake wrote:
>>> In the meantime, where do we stand on our goal of disabling in-tree builds?
>>
>> The view was largely positive when we discussed it. So I think it just
>> needs someone to step up with a patch proposal, and at the start of the
>> dev cycle is a good time for such a change i guess.
>
> Pitfalls to watch out for include checking whether any of:
> * the tests/vm scripting for the BSDs
> * various travis/etc CI configs
> * etc
* most of roms/
> are currently using in-tree builds.
> Paolo will also need to update his coverity build config.
>
> thanks
> -- PMM
>
prev parent reply other threads:[~2019-05-08 5:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-02 22:30 [Qemu-devel] [PULL 0/2] slirp: move slirp as git submodule project Samuel Thibault
2019-05-02 22:30 ` Samuel Thibault
2019-05-02 22:30 ` [Qemu-devel] [PULL 1/2] build-sys: pass CFLAGS & LDFLAGS to subdir-slirp Samuel Thibault
2019-05-02 22:30 ` Samuel Thibault
2019-05-02 22:30 ` [Qemu-devel] [PULL 2/2] build-sys: move slirp as git submodule project Samuel Thibault
2019-05-03 12:54 ` [Qemu-devel] [PULL 0/2] slirp: " Peter Maydell
2019-05-03 12:54 ` Peter Maydell
2019-05-03 15:05 ` Philippe Mathieu-Daudé
2019-05-03 15:05 ` Philippe Mathieu-Daudé
2019-05-03 15:12 ` Peter Maydell
2019-05-03 15:12 ` Peter Maydell
2019-05-07 14:11 ` Eric Blake
2019-05-07 14:19 ` Daniel P. Berrangé
2019-05-07 17:01 ` Peter Maydell
2019-05-08 5:48 ` Philippe Mathieu-Daudé [this message]
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=f6bb0085-34a3-7b65-da19-b78cd71e9630@redhat.com \
--to=philmd@redhat.com \
--cc=berrange@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=marcandre.lureau@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=samuel.thibault@ens-lyon.org \
--cc=stefanha@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).