From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Brad Smith" <brad@comstyle.com>
Subject: Re: [Qemu-devel] [PATCH] maintainers: Add myself as a OpenBSD maintainer
Date: Fri, 16 Feb 2018 17:44:05 +0000 [thread overview]
Message-ID: <20180216174405.GN3181@redhat.com> (raw)
In-Reply-To: <CAFEAcA9ZtLWzGZvF7O8WxJzoYghJwCa-EMMNqdk6YNpkvuaeEg@mail.gmail.com>
On Fri, Feb 16, 2018 at 05:37:32PM +0000, Peter Maydell wrote:
> On 16 February 2018 at 17:30, Philippe Mathieu-Daudé <f4bug@amsat.org> 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.
>
> I do include OpenBSD in my set of build/tests for merges.
There's also "make vm-build-openbsd" for devs who want to test easily in
an OpenBSD VM, or investigate brokeness.
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:[~2018-02-16 17:44 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é [this message]
2018-02-16 17:41 ` Kamil Rytarowski
2018-02-16 17:44 ` Philippe Mathieu-Daudé
2018-02-23 8:33 ` Fam Zheng
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=20180216174405.GN3181@redhat.com \
--to=berrange@redhat.com \
--cc=brad@comstyle.com \
--cc=f4bug@amsat.org \
--cc=peter.maydell@linaro.org \
--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 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.