From: Blue Swirl <blauwirbel@gmail.com>
To: "Andreas Färber" <andreas.faerber@web.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PULL 00/10] Fixes for Cocoa backend
Date: Wed, 15 Jun 2011 22:31:02 +0300 [thread overview]
Message-ID: <BANLkTimraf_cJfS=40cJ=BMN_vtLh7kUWg@mail.gmail.com> (raw)
In-Reply-To: <1308014527-60251-1-git-send-email-andreas.faerber@web.de>
On Tue, Jun 14, 2011 at 4:21 AM, Andreas Färber <andreas.faerber@web.de> wrote:
> Hello,
>
> I've collected a number of warning and usability fixes for the Cocoa frontend
> and Darwin host. Please pull.
>
> Cc: Blue Swirl <blauwirbel@gmail.com>
Thanks, pulled.
> The following changes since commit 0b862cedf36d927818c50584ddd611b0370673df:
>
> configure: Detect and don't try to use older libcurl (2011-06-13 21:16:27 +0200)
>
> are available in the git repository at:
> git://repo.or.cz/qemu/afaerber.git cocoa-for-upstream
>
> Alexandre Raymond (5):
> Fix compilation warning due to incorrectly specified type
> Cocoa: avoid displaying window when command-line contains '-h' or
> '-help'
> Remove warning in printf due to type mismatch
> configure: Fix check for fdatasync()
> Darwin: Fix compilation warning regarding the deprecated daemon()
> function
>
> Andreas Färber (4):
> Fix libfdt warnings on Darwin
> cocoa: Provide central qemu_main() prototype
> cocoa: Revert dependency on VNC
> cocoa: Avoid warning related to multiple handleEvent: definitions
>
> Tristan Gingold (1):
> cocoa: do not create a spurious window for -version
>
> Makefile.objs | 2 +-
> audio/coreaudio.c | 2 +-
> configure | 8 +++++++-
> libfdt_env.h | 8 ++------
> osdep.h | 1 +
> oslib-posix.c | 16 ++++++++++++++++
> qemu-common.h | 5 +++++
> qemu-nbd.c | 2 +-
> target-lm32/translate.c | 2 +-
> ui/cocoa.m | 25 ++++++++++++++++++-------
> 10 files changed, 53 insertions(+), 18 deletions(-)
>
> --
> 1.7.5.3
>
>
prev parent reply other threads:[~2011-06-15 19:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-14 1:21 [Qemu-devel] [PULL 00/10] Fixes for Cocoa backend Andreas Färber
2011-06-14 1:21 ` [Qemu-devel] [PATCH 01/10] cocoa: do not create a spurious window for -version Andreas Färber
2011-06-14 1:21 ` [Qemu-devel] [PATCH 02/10] Fix compilation warning due to incorrectly specified type Andreas Färber
2011-06-14 1:22 ` [Qemu-devel] [PATCH 03/10] Cocoa: avoid displaying window when command-line contains '-h' or '-help' Andreas Färber
2011-06-14 1:22 ` [Qemu-devel] [PATCH 04/10] Remove warning in printf due to type mismatch Andreas Färber
2011-06-14 1:22 ` [Qemu-devel] [PATCH 05/10] configure: Fix check for fdatasync() Andreas Färber
2011-06-14 1:22 ` [Qemu-devel] [PATCH 06/10] Fix libfdt warnings on Darwin Andreas Färber
2011-06-14 1:22 ` [Qemu-devel] [PATCH 07/10] cocoa: Provide central qemu_main() prototype Andreas Färber
2011-06-14 1:22 ` [Qemu-devel] [PATCH 08/10] cocoa: Revert dependency on VNC Andreas Färber
2011-06-14 1:22 ` [Qemu-devel] [PATCH 09/10] cocoa: Avoid warning related to multiple handleEvent: definitions Andreas Färber
2011-06-14 1:22 ` [Qemu-devel] [PATCH 10/10] Darwin: Fix compilation warning regarding the deprecated daemon() function Andreas Färber
2011-06-27 14:48 ` [Qemu-devel] [PATCH 08/10] cocoa: Revert dependency on VNC Jes Sorensen
2011-06-15 19:31 ` Blue Swirl [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='BANLkTimraf_cJfS=40cJ=BMN_vtLh7kUWg@mail.gmail.com' \
--to=blauwirbel@gmail.com \
--cc=andreas.faerber@web.de \
--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).