From: Paolo Bonzini <pbonzini@redhat.com>
To: "Peter Maydell" <peter.maydell@linaro.org>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: "Miroslav Rezanina" <mrezanin@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [PATCH] docs: Fix virtiofsd.1 location
Date: Thu, 13 Feb 2020 11:31:21 +0100 [thread overview]
Message-ID: <20a55761-f76a-b897-4f76-8bc95fdc1374@redhat.com> (raw)
In-Reply-To: <CAFEAcA97NfPA+yZThojcaYWqdS8kvFtDNYJRn96iRuRMaU-uMg@mail.gmail.com>
On 12/02/20 18:51, Peter Maydell wrote:
> On Wed, 12 Feb 2020 at 16:51, Philippe Mathieu-Daudé <philmd@redhat.com> wrote:
>> We stopped testing in-tree builds 2 months ago:
>>
>> commit bc4486fb233573e77b6e9ad6d6379afb5e37ad8c
>> Author: Paolo Bonzini <pbonzini@redhat.com>
>> Date: Wed Dec 11 15:33:49 2019 +0100
>>
>> ci: build out-of-tree
>>
>> Most developers are using out-of-tree builds and it was discussed
>> in the past to only allow those. To prepare for the transition,
>> use out-of-tree builds in all continuous integration jobs.
>
> I'd missed that. Paolo, do you have a plan for following
> through and actively forbidding in-tree-builds, if that's
> the route we're taking ?
I can follow up on that, yes.
Paolo
prev parent reply other threads:[~2020-02-13 10:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1908428819.7192207.1581512184275.JavaMail.zimbra@redhat.com>
2020-02-12 13:16 ` [PATCH] docs: Fix virtiofsd.1 location Miroslav Rezanina
2020-02-12 14:18 ` Peter Maydell
2020-02-12 14:26 ` Dr. David Alan Gilbert
2020-02-12 14:28 ` Daniel P. Berrangé
2020-02-12 16:02 ` Peter Maydell
2020-02-12 16:51 ` Philippe Mathieu-Daudé
2020-02-12 17:51 ` Peter Maydell
2020-02-13 10:31 ` Paolo Bonzini [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=20a55761-f76a-b897-4f76-8bc95fdc1374@redhat.com \
--to=pbonzini@redhat.com \
--cc=berrange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=mrezanin@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.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).