On 23/10/15 19:02, Dr. David Alan Gilbert wrote:
> * Stefan Hajnoczi (stefa...@gmail.com) wrote:
>> On Thu, Oct 22, 2015 at 03:30:34PM +0200, Lluís Vilanova wrote:
>>> Markus Armbruster writes:
>>>
Lluís Vilanova writes:
>>> [...]
> So, is there any agreement on what should be used? If so
On Fri, Oct 23, 2015 at 07:34:50PM +0200, Lluís Vilanova wrote:
> Stefan Hajnoczi writes:
>
> > On Thu, Oct 22, 2015 at 03:30:34PM +0200, Lluís Vilanova wrote:
> >> Markus Armbruster writes:
> >>
> >> > Lluís Vilanova writes:
> >> [...]
> >> >> So, is there any agreement on what should be used?
Stefan Hajnoczi writes:
> On Thu, Oct 22, 2015 at 03:30:34PM +0200, Lluís Vilanova wrote:
>> Markus Armbruster writes:
>>
>> > Lluís Vilanova writes:
>> [...]
>> >> So, is there any agreement on what should be used? If so, could that
>> >> please be
>> >> added to CODING_STYLE?
>>
>> > I think
* Stefan Hajnoczi (stefa...@gmail.com) wrote:
> On Thu, Oct 22, 2015 at 03:30:34PM +0200, Lluís Vilanova wrote:
> > Markus Armbruster writes:
> >
> > > Lluís Vilanova writes:
> > [...]
> > >> So, is there any agreement on what should be used? If so, could that
> > >> please be
> > >> added to CO
On 10/23/15 18:01, Stefan Hajnoczi wrote:
> On Thu, Oct 22, 2015 at 03:30:34PM +0200, Lluís Vilanova wrote:
>> Markus Armbruster writes:
>>
>>> Lluís Vilanova writes:
>> [...]
So, is there any agreement on what should be used? If so, could that
please be
added to CODING_STYLE?
>>
>
On Thu, Oct 22, 2015 at 03:30:34PM +0200, Lluís Vilanova wrote:
> Markus Armbruster writes:
>
> > Lluís Vilanova writes:
> [...]
> >> So, is there any agreement on what should be used? If so, could that
> >> please be
> >> added to CODING_STYLE?
>
> > I think HACKING would be a better fit.
>
>
Markus Armbruster writes:
> Lluís Vilanova writes:
[...]
>> So, is there any agreement on what should be used? If so, could that please
>> be
>> added to CODING_STYLE?
> I think HACKING would be a better fit.
What about this? (at the end of HACKING) Feel free to add references to other
functio
On 21 October 2015 at 17:48, Markus Armbruster wrote:
> Lluís Vilanova writes:
>
>> Hi,
>>
>> I was wondering what is the proper way (or ways, depending on the subsystem)
>> of
>> reporting and signalling errors in QEMU. The coding style file does not seem
>> to
>> mention it, and the code uses
Eric Blake writes:
> On 10/21/2015 09:03 AM, Lluís Vilanova wrote:
>> Hi,
>>
>> I was wondering what is the proper way (or ways, depending on the subsystem)
>> of
>> reporting and signalling errors in QEMU. The coding style file does not seem
>> to
>> mention it, and the code uses all kinds of
Lluís Vilanova writes:
> Hi,
>
> I was wondering what is the proper way (or ways, depending on the subsystem)
> of
> reporting and signalling errors in QEMU. The coding style file does not seem
> to
> mention it, and the code uses all kinds of forms for that:
>
> * printf + exit(1)
> * fprintf(
On 10/21/2015 09:03 AM, Lluís Vilanova wrote:
> Hi,
>
> I was wondering what is the proper way (or ways, depending on the subsystem)
> of
> reporting and signalling errors in QEMU. The coding style file does not seem
> to
> mention it, and the code uses all kinds of forms for that:
>
> * printf
Hi,
I was wondering what is the proper way (or ways, depending on the subsystem) of
reporting and signalling errors in QEMU. The coding style file does not seem to
mention it, and the code uses all kinds of forms for that:
* printf + exit(1)
* fprintf(stderr) + exit(1)
* error_report + exit(1)
*
12 matches
Mail list logo
