From: Avi Kivity <avi@qumranet.com>
To: jyoung5@us.ibm.com
Cc: kvm-ppc-devel@lists.sourceforge.net, kvm-devel@lists.sourceforge.net
Subject: Re: [kvm-ppc-devel] [kvm-devel] [PATCH] Add
Date: Wed, 26 Mar 2008 16:41:56 +0000 [thread overview]
Message-ID: <47EA7CD4.8010604@qumranet.com> (raw)
In-Reply-To: <1206472172.12682.3.camel@thinkpadL>
Jerone Young wrote:
> Yeah. This could "potentially" cause hell for users (non developers)
> down the road. I'm just going to keep this patch in my queue for myself,
> so no one will complain about warnings from my patches anymore.
>
> I think having a --developer flag to configure could work, but we would
> then need separate file for including the CFLAG, this would just clutter
> things more.
>
One other option is to enable -Werror by default, and have a
--disable-werror configure flag. It means we'll get better coverage,
but the user experience when it breaks will be worse.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
kvm-ppc-devel mailing list
kvm-ppc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-ppc-devel
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@qumranet.com>
To: jyoung5@us.ibm.com
Cc: kvm-ppc-devel@lists.sourceforge.net, kvm-devel@lists.sourceforge.net
Subject: Re: [kvm-ppc-devel] [PATCH] Add -Werror to libkvm compile
Date: Wed, 26 Mar 2008 18:41:56 +0200 [thread overview]
Message-ID: <47EA7CD4.8010604@qumranet.com> (raw)
In-Reply-To: <1206472172.12682.3.camel@thinkpadL>
Jerone Young wrote:
> Yeah. This could "potentially" cause hell for users (non developers)
> down the road. I'm just going to keep this patch in my queue for myself,
> so no one will complain about warnings from my patches anymore.
>
> I think having a --developer flag to configure could work, but we would
> then need separate file for including the CFLAG, this would just clutter
> things more.
>
One other option is to enable -Werror by default, and have a
--disable-werror configure flag. It means we'll get better coverage,
but the user experience when it breaks will be worse.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
next prev parent reply other threads:[~2008-03-26 16:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-24 18:44 [kvm-ppc-devel] [PATCH] Add -Werror to libkvm compile Jerone Young
2008-03-24 18:44 ` Jerone Young
2008-03-24 19:42 ` [kvm-ppc-devel] " Segher Boessenkool
2008-03-24 19:42 ` Segher Boessenkool
2008-03-25 16:33 ` [kvm-ppc-devel] [kvm-devel] [PATCH] Add -Werror to Jerone Young
2008-03-25 16:33 ` [kvm-ppc-devel] [PATCH] Add -Werror to libkvm compile Jerone Young
2008-03-25 17:08 ` [kvm-ppc-devel] [kvm-devel] [PATCH] Add -Werror Avi Kivity
2008-03-25 17:08 ` [kvm-ppc-devel] [PATCH] Add -Werror to libkvm compile Avi Kivity
2008-03-25 19:09 ` [kvm-ppc-devel] [kvm-devel] [PATCH] Add Jerone Young
2008-03-25 19:09 ` [kvm-ppc-devel] [PATCH] Add -Werror to libkvm compile Jerone Young
2008-03-26 16:41 ` Avi Kivity [this message]
2008-03-26 16:41 ` Avi Kivity
2008-03-24 20:28 ` [kvm-ppc-devel] [kvm-devel] [PATCH] Add -Werror to libkvm Anthony Liguori
2008-03-24 20:28 ` [PATCH] Add -Werror to libkvm compile Anthony Liguori
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=47EA7CD4.8010604@qumranet.com \
--to=avi@qumranet.com \
--cc=jyoung5@us.ibm.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=kvm-ppc-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.