From: Paolo Bonzini <pbonzini@redhat.com>
To: Jani Nikula <jani.nikula@linux.intel.com>,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Cc: corbet@lwn.net
Subject: Re: [PATCH 0/5] kernel-doc tweaks and cleanup of rST vs. non-rST backends
Date: Wed, 4 Jan 2017 16:13:32 +0100 [thread overview]
Message-ID: <9b78f94a-e27d-b463-2fe4-a307d8c008b8@redhat.com> (raw)
In-Reply-To: <87bmvoihyk.fsf@intel.com>
On 03/01/2017 10:57, Jani Nikula wrote:
> On Mon, 02 Jan 2017, Paolo Bonzini <pbonzini@redhat.com> wrote:
>> Hi,
>>
>> these patches are the result of my experiments with using kernel-doc
>> for QEMU's documentation. Patches 1 and 2 should be relatively
>> straightforward, as they are simple bugfixes. Patches 3 to 5, instead,
>> are making the docbook backend (and the others too) more consistent with
>> the input and output of the rST backend.
>
> I did not test the patches, and for sure I will not attempt reviewing
> perl, but at a high level the changes seem sensible.
>
> Acked-by: Jani Nikula <jani.nikula@intel.com>
Thanks---Perl's not that bad, come on! :)
>> I am not sure what is the state of the kernel-doc non-rST backends;
>> but there are still several books using the docbook workflow, so I'm
>> trying my luck and sending the patches anyway. :)
>
> Obviously reStructuredText is the main output now and has to work, and
> DocBook is still used as you say, but hopefully you sneaked in
> regressions for the other formats so we can gauge if anyone cares! ;)
Couldn't expect any other deprecation plan from a graphics guy!
FWIW I tested building the Sphinx and DocBook books and eyeballed the
output for both of them. I also tested manually the list backend on toy
testcases, and of course it is used by docproc when building DocBook
manuals. I didn't test the other backends.
Paolo
next prev parent reply other threads:[~2017-01-04 15:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-02 15:22 Paolo Bonzini
2017-01-02 15:22 ` [PATCH 1/5] kernel-doc: cleanup parameter type in function-typed arguments Paolo Bonzini
2017-01-02 15:22 ` [PATCH 2/5] kernel-doc: strip attributes even if they have an argument Paolo Bonzini
2017-01-02 15:22 ` [PATCH 3/5] kernel-doc: include parameter type in docbook output Paolo Bonzini
2017-01-02 15:22 ` [PATCH 4/5] kernel-doc: make member highlighting available in all backends Paolo Bonzini
2017-01-02 15:22 ` [PATCH 5/5] kernel-doc: make highlights more homogenous for the various backends Paolo Bonzini
2017-01-03 9:57 ` [PATCH 0/5] kernel-doc tweaks and cleanup of rST vs. non-rST backends Jani Nikula
2017-01-04 15:13 ` Paolo Bonzini [this message]
2017-01-04 15:40 ` Jani Nikula
2017-01-04 22:06 ` Jonathan Corbet
2017-01-23 13:42 ` Markus Heiser
2017-01-23 13:58 ` Paolo Bonzini
2017-01-23 14:38 ` Markus Heiser
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=9b78f94a-e27d-b463-2fe4-a307d8c008b8@redhat.com \
--to=pbonzini@redhat.com \
--cc=corbet@lwn.net \
--cc=jani.nikula@linux.intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®