From: Peter Maydell <peter.maydell@linaro.org>
To: Programmingkid <programmingkidx@gmail.com>
Cc: Gerd Hoffmann <kraxel@redhat.com>,
qemu-devel qemu-devel <qemu-devel@nongnu.org>,
Patch Tracking <patches@linaro.org>
Subject: Re: [Qemu-devel] [PATCH 0/5] audio/coreaudio.c: Fix deprecation warnings
Date: Tue, 1 Dec 2015 16:39:54 +0000 [thread overview]
Message-ID: <CAFEAcA_3urDcsr7RE3pTJv6ATCR2=GLydcrFk+x9Y--64GvcQA@mail.gmail.com> (raw)
In-Reply-To: <82FD3D54-D542-4AC9-85CD-B7AF78E9B96B@gmail.com>
On 1 December 2015 at 16:27, Programmingkid <programmingkidx@gmail.com> wrote:
> All the patches applied and compiled without problem on Mac OS 10.6.8.
> I played video and mp3 files in QEMU running a Windows XP guest. They
> all played perfectly.
Cool, thanks for the testing.
> I really was against the idea of removing Mac OS 10.5 support when I
> first heard the idea. But I did think about it before saying anything.
> I personally started out building QEMU on Mac OS 10.3. But that was
> years ago. Technology has moved on. Everyone wants to run their emulator
> on the fastest hardware they have. This hardware is probably not going
> to include anything running Mac OS 10.5. Removing Mac OS 10.5 support
> might be a good idea. I don't think we would inconvenience anyone.
> The only evidence I found of someone using Mac OS 10.5 to build QEMU
> was from 2012.
Yep. I actually would be happy retaining the 10.5 support even
for a single user, provided that that user was interacting with
us on qemu-devel and testing that our code still builds on their
setup and so on. That's why I propose to announce the deprecation
in the release notes, so if such a person exists they can come and
talk to us about it.
> We are only removing support for Mac OS 10.5 because of a warning
> message that appears during compilation. We could just disable
> warnings for that file. But the depreciated audio functions might
> not be around in the future, so probably better to say goodbye to
> them now before they cause real problems.
Note that this patch set does *not* drop 10.5 support -- the 10.5
versions of the functions are all present so in theory it should
build fine there. The only problem is that (as usual) nobody
is actually testing that it really does compile on 10.5.
thanks
-- PMM
prev parent reply other threads:[~2015-12-01 16:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-28 21:55 [Qemu-devel] [PATCH 0/5] audio/coreaudio.c: Fix deprecation warnings Peter Maydell
2015-11-28 21:55 ` [Qemu-devel] [PATCH 1/5] audio/coreaudio.c: Factor out use of AudioHardwareGetProperty Peter Maydell
2015-11-28 21:55 ` [Qemu-devel] [PATCH 2/5] audio/coreaudio.c: Use new-in-OSX-10.6 API for getting default voice Peter Maydell
2015-11-28 21:55 ` [Qemu-devel] [PATCH 3/5] audio/coreaudio.c: Factor out uses of AudioDeviceGet/SetProperty Peter Maydell
2015-11-28 21:55 ` [Qemu-devel] [PATCH 4/5] audio/coreaudio.c: Use new-in-OSX-10.6 APIs when available Peter Maydell
2015-11-28 21:55 ` [Qemu-devel] [PATCH 5/5] audio/coreaudio.c: Avoid deprecated AudioDeviceAdd/RemoveIOProc APIs Peter Maydell
2015-12-01 16:27 ` [Qemu-devel] [PATCH 0/5] audio/coreaudio.c: Fix deprecation warnings Programmingkid
2015-12-01 16:39 ` Peter Maydell [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='CAFEAcA_3urDcsr7RE3pTJv6ATCR2=GLydcrFk+x9Y--64GvcQA@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=kraxel@redhat.com \
--cc=patches@linaro.org \
--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).