From: Kamil Rytarowski <n54@gmx.com>
To: "Antonio Huete Jiménez" <tuxillo@quantumachine.net>,
qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org
Subject: Re: [Qemu-devel] DragonFly BSD support
Date: Wed, 14 Jun 2017 19:50:11 +0200 [thread overview]
Message-ID: <d3d7529a-2d0c-d5e7-1634-4aa16546eef8@gmx.com> (raw)
In-Reply-To: <20170614105547.Horde.Qq_wt1XJCR6spCHFrm8xE9K@www.quantumachine.net>
[-- Attachment #1: Type: text/plain, Size: 825 bytes --]
On 14.06.2017 12:55, Antonio Huete Jiménez wrote:
>
> Hi all,
>
> According to 2.9 changelog page, DragonFly BSD will be listed as
> unsupported with the possibility of dropping support completely in the
> future:
>
> http://wiki.qemu.org/ChangeLog/2.9
>
> I'd like to volunteer so that qemu can keep DragonFly BSD as a supported
> platform.
> Could you please let me know the requirements needed to do so?
>
> Best regards,
> Antonio Huete
>
>
Are there any local patches for qemu in your ports tree?
Please add yourself to MAINTAINERS and set DragonFly as maintained in
"configure".
There is an option to establish a BSD pull-request queue (as a public
group on GitHub?) and share it for BSD-specific patches. I work on
NetBSD and we still need someone at least for FreeBSD/OpenBSD.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2017-06-14 17:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-14 10:55 [Qemu-devel] DragonFly BSD support Antonio Huete Jiménez
2017-06-14 17:50 ` Kamil Rytarowski [this message]
2017-06-15 10:15 ` Peter Maydell
2017-06-15 18:09 ` John Snow
2017-06-15 18:18 ` 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=d3d7529a-2d0c-d5e7-1634-4aa16546eef8@gmx.com \
--to=n54@gmx.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=tuxillo@quantumachine.net \
/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).