From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:46185) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SukQB-0006Jn-5G for qemu-devel@nongnu.org; Fri, 27 Jul 2012 09:17:39 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SukPx-0001Ee-C5 for qemu-devel@nongnu.org; Fri, 27 Jul 2012 09:17:35 -0400 Received: from cantor2.suse.de ([195.135.220.15]:40125 helo=mx2.suse.de) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SukPx-0001EN-5q for qemu-devel@nongnu.org; Fri, 27 Jul 2012 09:17:21 -0400 Message-ID: <501294DB.1050304@suse.de> Date: Fri, 27 Jul 2012 15:17:15 +0200 From: =?ISO-8859-1?Q?Andreas_F=E4rber?= MIME-Version: 1.0 References: <1343249431-9245-1-git-send-email-lcapitulino@redhat.com> <87ehnyv7p8.fsf@blackfin.pond.sub.org> <50116A48.1050307@redhat.com> <20120726133724.293bf8b1@doriath.home> In-Reply-To: <20120726133724.293bf8b1@doriath.home> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] [RFC 00/14]: add printf-like human msg to error_set() List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Luiz Capitulino Cc: peter.maydell@linaro.org, Paolo Bonzini , aliguori@us.ibm.com, Markus Armbruster , qemu-devel@nongnu.org Am 26.07.2012 18:37, schrieb Luiz Capitulino: > On Thu, 26 Jul 2012 18:03:20 +0200 > Paolo Bonzini wrote: >=20 >> Il 26/07/2012 17:54, Markus Armbruster ha scritto: >>> Unlike Anthony, I think this is a move in the right direction. >> >> Me too, but I would like to understand how it fits with the >> qapi-schema-errors.json. Do we actually need a schema if the messages >> are flat? >=20 > Yes, we need it because we still an error object to obey (ie. the data = member). >=20 > But we're talking about dropping that, so it might be possible to kill > the schema. I'm not so familiar with how all this error infrastructure is plugged together... In a different thread that I mentioned recently (and still haven't found in my inbox), we were talking about changing the JSON encoding of errors where unused by libvirt. Specifically we were talking about having a field for the canonical QOM path of the affected object in place of the often-empty device ID. Are you now discussing to drop any such elaborated QMP schemes in place of just one non-parsable human error message string? Andreas --=20 SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N=FCrnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imend=F6rffer; HRB 16746 AG N=FCrnbe= rg