From: Stefan Hajnoczi <stefanha@gmail.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] configure: check for -Wendif-labels support
Date: Wed, 18 May 2011 08:45:52 +0100 [thread overview]
Message-ID: <BANLkTikR=RG9QTmKsJGPRAb-YJ78QgiDJA@mail.gmail.com> (raw)
In-Reply-To: <1305666523-374-1-git-send-email-vapier@gentoo.org>
On Tue, May 17, 2011 at 10:08 PM, Mike Frysinger <vapier@gentoo.org> wrote:
> Older gcc compilers do not support -Wendif-labels, so move it from the
> hardcoded list to the dynamically detected list.
>
> Signed-off-by: Mike Frysinger <vapier@gentoo.org>
> ---
> configure | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
Reviewed-by: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
next prev parent reply other threads:[~2011-05-18 7:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-17 21:08 [Qemu-devel] [PATCH] configure: check for -Wendif-labels support Mike Frysinger
2011-05-18 7:45 ` Stefan Hajnoczi [this message]
2011-06-03 21:50 ` Aurelien Jarno
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='BANLkTikR=RG9QTmKsJGPRAb-YJ78QgiDJA@mail.gmail.com' \
--to=stefanha@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=vapier@gentoo.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).