From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1L17Yk-0006gj-8I
	for qemu-devel@nongnu.org; Fri, 14 Nov 2008 17:54:38 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1L17Yj-0006gX-DU
	for qemu-devel@nongnu.org; Fri, 14 Nov 2008 17:54:37 -0500
Received: from [199.232.76.173] (port=55997 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1L17Yj-0006gU-AU
	for qemu-devel@nongnu.org; Fri, 14 Nov 2008 17:54:37 -0500
Received: from mail2.shareable.org ([80.68.89.115]:34504)
	by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32)
	(Exim 4.60) (envelope-from <jamie@shareable.org>) id 1L17Yj-0003Yk-3D
	for qemu-devel@nongnu.org; Fri, 14 Nov 2008 17:54:37 -0500
Date: Fri, 14 Nov 2008 22:54:35 +0000
From: Jamie Lokier <jamie@shareable.org>
Subject: Re: [Qemu-devel] Re: [PATCH 0/5] Add "info capabilities" monitor
	command
Message-ID: <20081114225434.GC19384@shareable.org>
References: <1226594763-2304-1-git-send-email-markmc@redhat.com>
	<491CF04F.5020408@codemonkey.ws>
	<20081114035122.GM2055@shareable.org>
	<1226678209.9332.92.camel@blaa>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1226678209.9332.92.camel@blaa>
Reply-To: qemu-devel@nongnu.org
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: Mark McLoughlin <markmc@redhat.com>
Cc: qemu-devel@nongnu.org

Mark McLoughlin wrote:
> > While we're at it, a section describing the monitor's capabilities so
> > we don't have to parse the _monitor's_ "help" output....  Oh, there I
> > go bike-shedding again :-)
> 
> Well, if "info capabilities" isn't implemented, simply having it fail is
> fine.

Sure, but there are other monitor commands, and sub-options to those
commands, which come and go depending on QEMU version and development
branch.  It would be good to describe those in a capabilities section,
as the only other option is trying the commands and discovering if
sub-options are supported that way.  It's possible to send TAB to the
monitor to get the output of command line completions sometimes, but
that's quite an ugly thing for a management tool to have to do.

-- Jamie