qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: anthony@codemonkey.ws
Cc: Kevin Wolf <kwolf@redhat.com>,
	Markus Armbruster <armbru@redhat.com>,
	qemu-devel@nongnu.org, Luiz Capitulino <lcapitulino@redhat.com>
Subject: Re: [Qemu-devel] Plan for error handling in QMP
Date: Fri, 27 Jul 2012 09:11:16 +0200	[thread overview]
Message-ID: <50123F14.80609@redhat.com> (raw)
In-Reply-To: <87ipdacrhj.fsf@codemonkey.ws>

Il 26/07/2012 20:22, anthony@codemonkey.ws ha scritto:
> 7. We need to make sure that anything we expose in 1.2 stays that way.
>    If we're dropping 'InvalidParameterType' as a class code, it should be
>    dropped in 1.2.  This could be achieved by making all existing codes
>    except for those in (5) report 'UnknownError' or something.[*]
> 
> [*] I took a little bit of license with these.  Hopefully it's not
> controversial.

Sounds great, just a note: I think that at the source level in 1.2 we
should not lose information on what was the "old" error type.  It will
guide the future conversion, also together with tables like
http://pastebin.com/kZtfFnFK.

So let's keep the names as "#define QERR_FOO UnknownError" for now.

Paolo

      parent reply	other threads:[~2012-07-27  7:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-26 18:22 [Qemu-devel] Plan for error handling in QMP anthony
2012-07-26 18:43 ` Luiz Capitulino
2012-07-26 18:47   ` Luiz Capitulino
2012-07-26 21:08     ` Anthony Liguori
2012-07-26 21:14       ` Luiz Capitulino
2012-07-26 22:47         ` Anthony Liguori
2012-07-27 14:24           ` Luiz Capitulino
2012-07-26 20:41 ` Eric Blake
2012-07-27  7:08   ` Paolo Bonzini
2012-07-26 21:16 ` Richard W.M. Jones
2012-07-27  7:08 ` Markus Armbruster
2012-07-27  7:11 ` Paolo Bonzini [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=50123F14.80609@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=armbru@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=lcapitulino@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).