From: Peter Maydell <peter.maydell@linaro.org>
To: QEMU Developers <qemu-devel@nongnu.org>
Cc: "G 3" <programmingkidx@gmail.com>,
"Andreas Färber" <andreas.faerber@web.de>,
"Alexander Graf" <agraf@suse.de>
Subject: [Qemu-devel] proposal: drop support for OSX 10.5 hosts from QEMU 2.6
Date: Sat, 28 Nov 2015 22:10:10 +0000 [thread overview]
Message-ID: <CAFEAcA8dQ612jzuLqfto2CeFty0V9UrX+WsN7n7MAPw-f1f5MQ@mail.gmail.com> (raw)
Hi. I'd like to propose that QEMU drops support for OSX 10.5 hosts
(and by extension for PPC OSX hosts) starting with QEMU 2.6.
The rationale here is basically that it's not tested at all as
far as I know -- I have been carefully retaining "only if 10.5"
ifdefs in the cocoa UI and audio code as I update it, but since
I have no 10.5 system to compile against it this support is
only theoretical and I wouldn't be terribly surprised to find
that it's actually broken. Dropping 10.5 would also allow us to drop
some ifdeffed code paths, but I wouldn't mind carrying them around if
we people were actually using them -- which I suspect nobody is!
OSX 10.5 is now over 8 years old; I think we'd have dropped it
some time ago if it wasn't the last PPC version.
My suggested plan would be:
* in the 2.5 release notes, announce that support for OSX 10.5 and PPC
hosts is deprecated and will be removed from QEMU 2.6 unless somebody
steps forward to help with testing
* at some point probably a little before 2.6 softfreeze, remove the
now unnecessary ifdeffery
Any disagreements? Am I wrong about nobody testing QEMU on 10.5?
thanks
-- PMM
next reply other threads:[~2015-11-28 22:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-28 22:10 Peter Maydell [this message]
2015-11-28 22:22 ` [Qemu-devel] proposal: drop support for OSX 10.5 hosts from QEMU 2.6 Alexander Graf
2015-12-17 11:35 ` 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=CAFEAcA8dQ612jzuLqfto2CeFty0V9UrX+WsN7n7MAPw-f1f5MQ@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=agraf@suse.de \
--cc=andreas.faerber@web.de \
--cc=programmingkidx@gmail.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).