From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1NCYFQ-0000Nc-Vl
	for qemu-devel@nongnu.org; Mon, 23 Nov 2009 07:42:29 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1NCYFM-0000L9-0o
	for qemu-devel@nongnu.org; Mon, 23 Nov 2009 07:42:28 -0500
Received: from [199.232.76.173] (port=49543 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1NCYFL-0000L1-QS
	for qemu-devel@nongnu.org; Mon, 23 Nov 2009 07:42:23 -0500
Received: from mx1.redhat.com ([209.132.183.28]:6861)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <lcapitulino@redhat.com>) id 1NCYFL-0000hY-80
	for qemu-devel@nongnu.org; Mon, 23 Nov 2009 07:42:23 -0500
Date: Mon, 23 Nov 2009 10:42:13 -0200
From: Luiz Capitulino <lcapitulino@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 00/10]: QError v4
Message-ID: <20091123104213.4b7f61f0@doriath>
In-Reply-To: <m3iqd48abi.fsf@crossbow.pond.sub.org>
References: <1258487037-24950-1-git-send-email-lcapitulino@redhat.com>
	<m33a4bes1c.fsf@crossbow.pond.sub.org>
	<4B04383A.9050101@linux.vnet.ibm.com>
	<m38we27rju.fsf@crossbow.pond.sub.org>
	<4B06C00F.3020107@codemonkey.ws>
	<m3zl6hc9ts.fsf@crossbow.pond.sub.org>
	<4B06E854.7080101@codemonkey.ws>
	<m3iqd48abi.fsf@crossbow.pond.sub.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org, kraxel@redhat.com

On Sat, 21 Nov 2009 11:02:41 +0100
Markus Armbruster <armbru@redhat.com> wrote:

> Now, what should a client do when it discovers the monitor command it
> needs to use has grown a new error?  Refuse to use the command for fear
> of having to present a sub-par error message to the user in case it
> fails?

 What's your solution for this problem?

> Yes, the client needs updating in such a scenario.  But since it's a
> normal, expected situation, I wouldn't call it a client bug.  And
> regardless how we call it, we better handle it gracefully.

 The best thing the client can do here is to print the error class.