From: Fam Zheng <famz@redhat.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: Kamil Rytarowski <n54@gmx.com>, Brad Smith <brad@comstyle.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] maintainers: Add myself as a OpenBSD maintainer
Date: Fri, 23 Feb 2018 16:33:15 +0800 [thread overview]
Message-ID: <20180223083315.GC31530@lemon.usersys.redhat.com> (raw)
In-Reply-To: <e625c026-2fa4-f3ea-d85e-080c65a4885f@amsat.org>
On Fri, 02/16 14:44, Philippe Mathieu-Daudé wrote:
> On 02/16/2018 02:41 PM, Kamil Rytarowski wrote:
> > On 16.02.2018 18:30, Philippe Mathieu-Daudé wrote:
> >> But before announcing the host OS being supported again, I'd rather see
> >> reproducible build/tests logs, in a (public - if possible) continuous
> >> integration system. Else it is hard to notice when it get broken.
> >>
> >
> > This is already done for FreeBSD, NetBSD and OpenBSD.
>
> We have the ability to run those, but afaik no CI are using them.
That's right. I can try enabling them on patchew, but my gut feeling is that
these still need to be optimized (especially, enabling persisted ccache like our
docker tests, so it is reasonably efficient for our limited resources).
Fam
next prev parent reply other threads:[~2018-02-23 8:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-16 16:46 [Qemu-devel] [PATCH] maintainers: Add myself as a OpenBSD maintainer Brad Smith
2018-02-16 17:12 ` Kamil Rytarowski
2018-02-16 17:30 ` Philippe Mathieu-Daudé
2018-02-16 17:37 ` Peter Maydell
2018-02-16 17:44 ` Daniel P. Berrangé
2018-02-16 17:41 ` Kamil Rytarowski
2018-02-16 17:44 ` Philippe Mathieu-Daudé
2018-02-23 8:33 ` Fam Zheng [this message]
2018-03-19 22:06 ` [Qemu-devel] make vm-test [was: [PATCH] maintainers: Add myself as a OpenBSD maintainer] Eric Blake
2018-03-21 8:11 ` Fam Zheng
2018-03-21 13:14 ` Eric Blake
2018-03-21 14:07 ` Fam Zheng
2018-02-23 14:41 ` [Qemu-devel] [PATCH] maintainers: Add myself as a OpenBSD maintainer Peter Maydell
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=20180223083315.GC31530@lemon.usersys.redhat.com \
--to=famz@redhat.com \
--cc=brad@comstyle.com \
--cc=f4bug@amsat.org \
--cc=n54@gmx.com \
--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).