Hi
On Thu, Nov 3, 2016 at 5:46 PM Markus Armbruster wrote:
> Marc-André Lureau writes:
>
> > If we want to have a very strict grammar, there is even more work needed
> to
> > cleanup the documentation. I don't fancy doing that work, it gives only
> low
> > benefits.
>
> Since I have pretty spec
Marc-André Lureau writes:
> Hi
>
> On Fri, Oct 28, 2016 at 7:45 PM Markus Armbruster wrote:
>
>> Marc-André Lureau writes:
>>
>> > As the name suggests, the qapi2texi script converts JSON QAPI
>> > description into a standalone texi file suitable for different target
>> > formats.
>> >
>> > It
Hi
On Fri, Oct 28, 2016 at 7:45 PM Markus Armbruster wrote:
> Marc-André Lureau writes:
>
> > As the name suggests, the qapi2texi script converts JSON QAPI
> > description into a standalone texi file suitable for different target
> > formats.
> >
> > It parses the following kind of blocks with
On 10/28/2016 11:44 AM, Markus Armbruster wrote:
> Marc-André Lureau writes:
>
>> As the name suggests, the qapi2texi script converts JSON QAPI
>> description into a standalone texi file suitable for different target
>> formats.
>>
>> It parses the following kind of blocks with some little variat
Marc-André Lureau writes:
> As the name suggests, the qapi2texi script converts JSON QAPI
> description into a standalone texi file suitable for different target
> formats.
>
> It parses the following kind of blocks with some little variations:
>
> ##
> # = Section
> # == Subsection
> #
>
As the name suggests, the qapi2texi script converts JSON QAPI
description into a standalone texi file suitable for different target
formats.
It parses the following kind of blocks with some little variations:
##
# = Section
# == Subsection
#
# Some text foo with *emphasis*
# 1. with a
