[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] [RFC] How should QEMU code handle include statements
- To: Stefan Weil <sw@xxxxxxxxxxx>
- From: Avi Kivity <avi@xxxxxxxxxx>
- Date: Tue, 21 Aug 2012 13:19:05 +0300
- Cc: peter.maydell@xxxxxxxxxx, jan.kiszka@xxxxxxxxxxx, mjt@xxxxxxxxxx, qemu-devel@xxxxxxxxxx, armbru@xxxxxxxxxx, blauwirbel@xxxxxxxxx, kraxel@xxxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx, i.mitsyanko@xxxxxxxxxxx, mdroth@xxxxxxxxxxxxxxxxxx, anthony.perard@xxxxxxxxxx, lersek@xxxxxxxxxx, stefanha@xxxxxxxxxxxxxxxxxx, stefano.stabellini@xxxxxxxxxxxxx, Igor Mammedov <imammedo@xxxxxxxxxx>, lcapitulino@xxxxxxxxxx, rth@xxxxxxxxxxx, kwolf@xxxxxxxxxx, aliguori@xxxxxxxxxx, mtosatti@xxxxxxxxxx, pbonzini@xxxxxxxxxx, afaerber@xxxxxxx
- Delivery-date: Tue, 21 Aug 2012 10:19:59 +0000
- List-id: Xen developer discussion <xen-devel.lists.xen.org>
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
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel
|
