From: Thomas Huth <1715203@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1715203] Re: Maintain Haiku support
Date: Fri, 30 Apr 2021 09:14:22 -0000 [thread overview]
Message-ID: <161977406339.10711.7061181283114798772.launchpad@gac.canonical.com> (raw)
In-Reply-To: 150463414707.19543.9931062189110648888.malonedeb@chaenomeles.canonical.com
** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1715203
Title:
Maintain Haiku support
Status in QEMU:
Fix Released
Bug description:
It was pointed out that the 2.10 release notes are pushing to drop
Haiku support. The qemu port is currently working as-is under Haiku.
Was there a reason this was recommended? Is there anything Haiku can
do to keep it from being dropped?
We're working on a docker container to cross-compile rust-lang for
Haiku, could this be of some use to qemu when complete?
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1715203/+subscriptions
prev parent reply other threads:[~2021-04-30 9:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-05 17:55 [Qemu-devel] [Bug 1715203] [NEW] Maintain Haiku support kallisti5
2017-09-05 18:08 ` Peter Maydell
2017-09-05 18:14 ` [Qemu-devel] [Bug 1715203] " kallisti5
2017-09-05 18:25 ` Peter Maydell
2017-09-05 19:00 ` kallisti5
2017-09-08 1:09 ` kallisti5
2020-09-05 9:43 ` Thomas Huth
2020-09-05 12:03 ` kallisti5
2020-09-05 14:46 ` kallisti5
2020-09-05 14:48 ` kallisti5
2020-09-05 15:19 ` kallisti5
2020-09-05 16:18 ` Thomas Huth
2020-09-06 14:45 ` kallisti5
2020-11-17 18:33 ` Thomas Huth
2021-04-30 9:14 ` Thomas Huth [this message]
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=161977406339.10711.7061181283114798772.launchpad@gac.canonical.com \
--to=1715203@bugs.launchpad.net \
--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).