On Mon, 15 Feb 2010 19:42:29 +0100
Markus Armbruster wrote:
> Anthony Liguori writes:
> > Thanks for the write-up. Here's my view of how error reporting ought
> > to work:
> >
> > 0) A user tries to do something via some piece of code that serves as
> > the UI. This may be the -device option
Anthony Liguori writes:
> Hi Markus,
>
> On 02/12/2010 11:48 AM, Markus Armbruster wrote:
>> Our QError conversions were pretty straightforward so far. For example,
>> when we found
>>
>> monitor_printf(mon, "device is not removable\n");
>>
>> in eject_device(), we created the o
On Fri, 12 Feb 2010 15:39:07 -0600
Anthony Liguori wrote:
> Hi Markus,
>
> On 02/12/2010 11:48 AM, Markus Armbruster wrote:
> > Our QError conversions were pretty straightforward so far. For example,
> > when we found
> >
> > monitor_printf(mon, "device is not removable\n");
>
Hi Markus,
On 02/12/2010 11:48 AM, Markus Armbruster wrote:
Our QError conversions were pretty straightforward so far. For example,
when we found
monitor_printf(mon, "device is not removable\n");
in eject_device(), we created the obvious QError class for it:
#define QERR_DEV
