From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([208.118.235.92]:34247)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <avi@redhat.com>) id 1T3lYV-0006lq-Lj
	for qemu-devel@nongnu.org; Tue, 21 Aug 2012 06:19:28 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <avi@redhat.com>) id 1T3lYU-0000M3-Dx
	for qemu-devel@nongnu.org; Tue, 21 Aug 2012 06:19:27 -0400
Received: from mx1.redhat.com ([209.132.183.28]:28028)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <avi@redhat.com>) id 1T3lYU-0000Lp-5e
	for qemu-devel@nongnu.org; Tue, 21 Aug 2012 06:19:26 -0400
Message-ID: <50336099.3040206@redhat.com>
Date: Tue, 21 Aug 2012 13:19:05 +0300
From: Avi Kivity <avi@redhat.com>
MIME-Version: 1.0
References: <1345419579-25499-1-git-send-email-imammedo@redhat.com>	<5031C2A3.3060800@weilnetz.de>
	<20120820134739.08bf6de4@thinkpad.mammed.net>
	<50329903.8000608@weilnetz.de>
In-Reply-To: <50329903.8000608@weilnetz.de>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] [RFC] How should QEMU code handle include
	statements
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Stefan Weil <sw@weilnetz.de>
Cc: peter.maydell@linaro.org, jan.kiszka@siemens.com, mjt@tls.msk.ru, qemu-devel@nongnu.org, armbru@redhat.com, blauwirbel@gmail.com, kraxel@redhat.com, xen-devel@lists.xensource.com, i.mitsyanko@samsung.com, mdroth@linux.vnet.ibm.com, anthony.perard@citrix.com, lersek@redhat.com, stefanha@linux.vnet.ibm.com, stefano.stabellini@eu.citrix.com, Igor Mammedov <imammedo@redhat.com>, lcapitulino@redhat.com, rth@twiddle.net, kwolf@redhat.com, aliguori@us.ibm.com, mtosatti@redhat.com, pbonzini@redhat.com, afaerber@suse.de

On 08/20/2012 11:07 PM, Stefan Weil wrote:

> While I personally prefer (1) and used it for my first contributions,
> QEMU introduced qemu-common.h. I had the impression that from then on
> QEMU preferred strategy (2). Obviously not everybody shares that
> impression.
> 
> Which strategy / rule do we want to use for QEMU code?

(1).


-- 
error compiling committee.c: too many arguments to function