From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Richard Henderson <richard.henderson@linaro.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [COMMITTED 0/3] build fixes
Date: Tue, 12 Jul 2022 11:13:05 +0100 [thread overview]
Message-ID: <Ys1JMetNPT47lpbV@redhat.com> (raw)
In-Reply-To: <20220712095901.212353-1-richard.henderson@linaro.org>
On Tue, Jul 12, 2022 at 03:28:58PM +0530, Richard Henderson wrote:
> This is a collection of fixes required to get CI back to green.
> Given that 2 of 3 apply to cirrus, I had to push them to staging to
> even try them. Since it worked, I've now pushed them to master.
FWIW, it is possible to test Cirrus CI fixes in your own personal
fork too, but it needs a little extra setup first, detailed in
.gitlab-ci.d/cirrus/README.rst
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2022-07-12 10:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-12 9:58 [COMMITTED 0/3] build fixes Richard Henderson
2022-07-12 9:58 ` [COMMITTED 1/3] gitlab-ci/cirrus: Update freebsd to python 3.9 packages Richard Henderson
2022-07-12 9:59 ` [COMMITTED 2/3] iotests: fix copy-before-write for macOS and FreeBSD Richard Henderson
2022-07-12 15:31 ` Warner Losh
2022-07-12 9:59 ` [COMMITTED 3/3] iotests/copy-before-write: specify required_fmts Richard Henderson
2022-07-12 10:13 ` Daniel P. Berrangé [this message]
2022-07-12 10:26 ` [COMMITTED 0/3] build fixes Richard Henderson
2022-07-12 10:31 ` Daniel P. Berrangé
2022-07-12 14:49 ` Warner Losh
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=Ys1JMetNPT47lpbV@redhat.com \
--to=berrange@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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 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.