From: Anthony Liguori <aliguori@us.ibm.com>
To: Glauber de Oliveira Costa <gcosta@redhat.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] Error message for device not found at blkif.py
Date: Wed, 18 Oct 2006 16:41:12 -0500 [thread overview]
Message-ID: <45369F78.4090409@us.ibm.com> (raw)
In-Reply-To: <20061018212846.GC16266@redhat.com>
Glauber de Oliveira Costa wrote:
> On Wed, Oct 18, 2006 at 03:59:30PM -0500, Anthony Liguori wrote:
>
>> Instead of throwing a VmError, could you subclass VmError with a more
>> specific error and throw that?
>>
> Fore sure I can. But what does this condition have so differently from
> others that justifies that for it only? Although I agree with you that
> such a specificiness is good, VmError is being thrown everywhere, meaning
> that your proposal would require touching a great amount of code change.
> Is there any plans/opposals for that?
>
>
BTW, check out tools/python/xen/xend/XendError.py for an example of
where we're doing this.
Regards,
Anthony Liguori
prev parent reply other threads:[~2006-10-18 21:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-18 20:08 [PATCH] Error message for device not found at blkif.py Glauber de Oliveira Costa
2006-10-18 20:59 ` Anthony Liguori
2006-10-18 21:28 ` Glauber de Oliveira Costa
2006-10-18 21:37 ` Anthony Liguori
2006-10-18 21:41 ` Anthony Liguori [this message]
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=45369F78.4090409@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=gcosta@redhat.com \
--cc=xen-devel@lists.xensource.com \
/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.