From: Paolo Bonzini <pbonzini@redhat.com>
To: "Thomas Huth" <thuth@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Andrew Jones" <drjones@redhat.com>,
"Richard Henderson" <richard.henderson@linaro.org>,
qemu-devel <qemu-devel@nongnu.org>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Cleber Rosa" <crosa@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: Serious doubts about Gitlab CI
Date: Tue, 30 Mar 2021 14:09:38 +0200 [thread overview]
Message-ID: <902a93ca-bd71-504b-fcf5-fec2480f9ec0@redhat.com> (raw)
In-Reply-To: <04e5e251-7a09-dcf6-82ad-31bf696bc248@redhat.com>
On 30/03/21 13:55, Thomas Huth wrote:
>
> Since the build system has been converted to meson, I think the
> configure script prefers to use the submodules instead of the distro
> packages. I've tried to remedy this a little bit here:
>
> https://gitlab.com/qemu-project/qemu/-/commit/db0108d5d846e9a8
>
> ... but new jobs of course will use the submodules again if the author
> is not careful.
Hmm... it should be the same (or if not it's a bug).
> Also I wonder whether we could maybe even get rid of the capstone and slirp submodules in QEMU now
At least for slirp, we probably want to stay more on the bleeding edge
which implies having to keep the submodule. Capstone and libfdt
probably can go.
Paolo
next prev parent reply other threads:[~2021-03-30 12:13 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-17 20:29 Serious doubts about Gitlab CI Philippe Mathieu-Daudé
2021-03-18 1:28 ` Bin Meng
2021-03-18 8:55 ` Philippe Mathieu-Daudé
2021-03-18 9:33 ` Daniel P. Berrangé
2021-03-18 9:50 ` Philippe Mathieu-Daudé
2021-03-18 10:28 ` Philippe Mathieu-Daudé
2021-03-19 5:34 ` Thomas Huth
2021-03-18 19:46 ` Stefan Hajnoczi
2021-03-18 19:52 ` John Snow
2021-03-18 20:53 ` Philippe Mathieu-Daudé
2021-03-18 20:30 ` Paolo Bonzini
2021-03-19 9:33 ` Stefan Hajnoczi
2021-03-19 9:41 ` Paolo Bonzini
2021-03-19 11:44 ` Philippe Mathieu-Daudé
2021-03-19 10:18 ` Andrew Jones
2021-03-19 10:59 ` Paolo Bonzini
2021-03-19 11:34 ` Philippe Mathieu-Daudé
2021-03-19 15:27 ` Wainer dos Santos Moschetta
2021-03-29 14:10 ` Stefan Hajnoczi
2021-03-30 11:19 ` Daniel P. Berrangé
2021-03-30 11:55 ` Thomas Huth
2021-03-30 12:09 ` Paolo Bonzini [this message]
2021-03-30 12:23 ` Philippe Mathieu-Daudé
2021-03-30 12:45 ` Paolo Bonzini
2021-03-30 13:12 ` Daniel P. Berrangé
2021-03-30 13:19 ` Paolo Bonzini
2021-03-30 13:27 ` Daniel P. Berrangé
2021-03-30 15:59 ` Warner Losh
2021-03-30 16:11 ` Peter Maydell
2021-03-30 16:24 ` Warner Losh
2021-03-30 16:10 ` Thomas Huth
2021-03-30 13:09 ` Daniel P. Berrangé
2021-03-30 12:09 ` Paolo Bonzini
2021-03-30 12:19 ` Peter Maydell
2021-03-30 12:33 ` Philippe Mathieu-Daudé
2021-03-30 13:19 ` Daniel P. Berrangé
2021-03-31 7:54 ` Thomas Huth
2021-03-31 9:31 ` Andrea Bolognani
2021-03-30 14:13 ` Stefan Hajnoczi
2021-03-30 14:23 ` Paolo Bonzini
2021-03-30 14:30 ` Daniel P. Berrangé
2021-03-30 14:09 ` Stefan Hajnoczi
2021-03-19 12:07 ` Markus Armbruster
2021-03-19 13:06 ` Thomas Huth
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=902a93ca-bd71-504b-fcf5-fec2480f9ec0@redhat.com \
--to=pbonzini@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=crosa@redhat.com \
--cc=drjones@redhat.com \
--cc=f4bug@amsat.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=stefanha@redhat.com \
--cc=thuth@redhat.com \
--cc=wainersm@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).