qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Butsykin <pbutsykin@odin.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Denis V. Lunev" <den@openvz.org>,
	Luiz Capitulino <lcapitulino@redhat.com>,
	QEMU Developers <qemu-devel@nongnu.org>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Pavel Butsykin <pbutsykin@virtuozzo.com>
Subject: Re: [Qemu-devel] [PATCH 3/3] monitor: added generation of documentation for hmp-commands-info.hx
Date: Fri, 28 Aug 2015 17:53:56 +0300	[thread overview]
Message-ID: <55E07604.8060902@odin.com> (raw)
In-Reply-To: <CAFEAcA-N1Bk1bP78MTG_7enDBp1L0NXD4nti-p70UaRdw0nrDA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1714 bytes --]



On 28.08.2015 11:19, Peter Maydell wrote:
> On 28 August 2015 at 08:00, Pavel Butsykin <pbutsykin@odin.com> wrote:
>>
>> On 27.08.2015 20:39, Peter Maydell wrote:
>>> On 12 August 2015 at 12:50, Denis V. Lunev <den@openvz.org> wrote:
>>>> From: Pavel Butsykin <pbutsykin@virtuozzo.com>
>>>>
>>>> It will be easier if you need to add info-commands to edit
>>>> only hmp-commands-info.hx, before this had to edit monitor.c and
>>>> hmp-commands.hx
>>>> diff --git a/hmp-commands-info.hx b/hmp-commands-info.hx
>>>> index 9ccb33f..81ae9d7 100644
>>>> --- a/hmp-commands-info.hx
>>>> +++ b/hmp-commands-info.hx
>>>> @@ -6,6 +6,9 @@ HXCOMM monitor info commands
>>>>    HXCOMM HXCOMM can be used for comments, discarded from both texi and C
>>>>
>>>>    STEXI
>>>> +@item info @var{subcommand}
>>>> +@findex info
>>>> +Show various information about the system state.
>>>>    @table @option
>>>>    ETEXI
>>>>
>>>> @@ -708,4 +711,5 @@ ETEXI
>>>>
>>>>    STEXI
>>>>    @end table
>>>> +@end table
>>>>    ETEXI
>>> Where does this extra "@end table" come from?
>>>
>>> thanks
>>> -- PMM
>> This "@end table" come from hmp-commands.hx and it's necessary to close tag
>> "@subsection Commands" from qemu-doc.texi
> If the tag is opened in qemu-doc.texi then I think
> qemu-doc.texi ought to be responsible for closing it.
>
> This may be related to a bug in the docs (as they are
> in master) where we close the table too early and so
> the 'info trace-events' and rocker related info subcommands
> aren't indented properly. (Also the rocker subcommands
> don't say "info $subcommand" the way the others do.)
>
> thanks
> -- PMM
You're right, the "@subsection Commands" is not required to close :) 
I'll fix it, thanks.

[-- Attachment #2: Type: text/html, Size: 2868 bytes --]

  reply	other threads:[~2015-08-28 14:55 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-12 11:50 [Qemu-devel] [PATCH v2 for 2.5 0/3] Move target- and device specific code from monitor Denis V. Lunev
2015-08-12 11:50 ` [Qemu-devel] [PATCH 1/3] hmp-commands-info: move info_cmds content out of monitor.c Denis V. Lunev
2015-08-27 17:40   ` Peter Maydell
2015-08-12 11:50 ` [Qemu-devel] [PATCH 2/3] monitor: remove target-specific code from monitor.c Denis V. Lunev
2015-08-27 17:31   ` Peter Maydell
2015-08-27 17:37     ` Denis V. Lunev
2015-08-28  9:21     ` Pavel Butsykin
2015-08-28 10:12       ` Peter Maydell
2015-08-28 14:58         ` Pavel Butsykin
2015-08-12 11:50 ` [Qemu-devel] [PATCH 3/3] monitor: added generation of documentation for hmp-commands-info.hx Denis V. Lunev
2015-08-27 17:39   ` Peter Maydell
2015-08-28  7:00     ` Pavel Butsykin
2015-08-28  8:19       ` Peter Maydell
2015-08-28 14:53         ` Pavel Butsykin [this message]
2015-08-18 23:50 ` [Qemu-devel] [PATCH v2 for 2.5 0/3] Move target- and device specific code from monitor Denis V. Lunev
2015-08-25  9:54 ` Denis V. Lunev
2015-08-27 11:27   ` Denis V. Lunev
2015-08-27 12:13     ` Peter Maydell
2015-08-27 12:34       ` Denis V. Lunev
2015-08-28 11:25 ` Markus Armbruster
  -- strict thread matches above, loose matches on Subject: below --
2015-07-02 16:18 [Qemu-devel] (no subject) Denis V. Lunev
2015-07-02 16:18 ` [Qemu-devel] [PATCH 3/3] monitor: added generation of documentation for hmp-commands-info.hx Denis V. Lunev

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=55E07604.8060902@odin.com \
    --to=pbutsykin@odin.com \
    --cc=den@openvz.org \
    --cc=lcapitulino@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=pbutsykin@virtuozzo.com \
    --cc=peter.maydell@linaro.org \
    --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).