From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=40561 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OCyMz-0006hn-SO for qemu-devel@nongnu.org; Fri, 14 May 2010 13:08:18 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OCyMr-0000w9-Eb for qemu-devel@nongnu.org; Fri, 14 May 2010 13:08:16 -0400 Received: from goliath.siemens.de ([192.35.17.28]:23756) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OCyMr-0000vz-4R for qemu-devel@nongnu.org; Fri, 14 May 2010 13:08:09 -0400 Message-ID: <4BED8377.7040000@siemens.com> Date: Fri, 14 May 2010 19:08:07 +0200 From: Jan Kiszka MIME-Version: 1.0 References: <1273086712-29163-1-git-send-email-lcapitulino@redhat.com> <1273086712-29163-2-git-send-email-lcapitulino@redhat.com> <4BED7FDC.7030208@siemens.com> <4BED8202.5020309@redhat.com> <4BED8224.9030604@redhat.com> In-Reply-To: <4BED8224.9030604@redhat.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Re: [PATCH 1/2] QMP: Introduce commands doc List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Avi Kivity Cc: "bazulay@redhat.com" , "juzhang@redhat.com" , "qemu-devel@nongnu.org" , "armbru@redhat.com" , Luiz Capitulino Avi Kivity wrote: > On 05/14/2010 08:01 PM, Avi Kivity wrote: >> On 05/14/2010 07:52 PM, Jan Kiszka wrote: >>>> In order not to compromise QMP adoption and make users' life easier, >>>> this commit adds a simple text documentation which fully describes >>>> all QMP supported commands. >>>> >>>> This is not ideal for a number of reasons (harder to maintain, >>>> text-only, etc) but does improve the current situation. >>> Even if it's temporary - maintaining it in a separate file looks rather >>> unhandy. >>> >>> Can't we generate the per-command documentation snippets also from >>> qemu-monitor.hx and merge them with a header/footer into some text file? >>> That .hx file is the one anyone adding/converting commands has to touch >>> anyway. >> If we do, then the generated documentation should be included in the >> patch changelog for review. >> > > I mean, a patch introducing or modifying a monitor command. The snippets should be readable by themselves. I'm only proposing to keep them in the central file, at the same location where the others are. There is no difference compared to existing monitor commands, we just add the third documentation snippet, this time for QMP. Distributing a generated QMP/qmp-commands.txt is another thing, maybe a useful one. Jan -- Siemens AG, Corporate Technology, CT T DE IT 1 Corporate Competence Center Embedded Linux