qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
	qemu-block@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>,
	Max Reitz <mreitz@redhat.com>
Subject: Re: [PATCH 1/3] qemu-nbd: Convert invocation documentation to rST
Date: Thu, 23 Jan 2020 06:43:15 -0600	[thread overview]
Message-ID: <c14e6614-4411-e4d1-daab-626e575450fb@redhat.com> (raw)
In-Reply-To: <20200116141511.16849-2-peter.maydell@linaro.org>

On 1/16/20 8:15 AM, Peter Maydell wrote:
> The qemu-nbd documentation is currently in qemu-nbd.texi in Texinfo
> format, which we present to the user as:
>   * a qemu-nbd manpage
>   * a section of the main qemu-doc HTML documentation
> 
> Convert the documentation to rST format, and present it to the user as:
>   * a qemu-nbd manpage
>   * part of the interop/ Sphinx manual
> 

As I have now posted a patch that conflicts with this 
(https://lists.gnu.org/archive/html/qemu-devel/2020-01/msg05118.html), 
and it needs a v2, I'm happy to do my rebase on top of this series, and 
stage these patches through my NBD tree if they don't land on master 
sooner via another path.

> 
> v1->v2:
>   * avoided some long lines in the Makefile
> ---
>   Makefile                               |  16 +-
>   MAINTAINERS                            |   1 +
>   docs/interop/conf.py                   |   4 +-
>   docs/interop/index.rst                 |   1 +
>   docs/interop/qemu-nbd.rst              | 263 +++++++++++++++++++++++++
>   docs/interop/qemu-option-trace.rst.inc |  30 +++
>   qemu-doc.texi                          |   6 -
>   qemu-nbd.texi                          | 214 --------------------
>   qemu-option-trace.texi                 |   4 +
>   9 files changed, 313 insertions(+), 226 deletions(-)
>   create mode 100644 docs/interop/qemu-nbd.rst
>   create mode 100644 docs/interop/qemu-option-trace.rst.inc
>   delete mode 100644 qemu-nbd.texi
> 

Reviewed-by: Eric Blake <eblake@redhat.com>

-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3226
Virtualization:  qemu.org | libvirt.org



  parent reply	other threads:[~2020-01-23 14:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-16 14:15 [PATCH 0/3] convert qemu-nbd, qemu-block-drivers to rST Peter Maydell
2020-01-16 14:15 ` [PATCH 1/3] qemu-nbd: Convert invocation documentation " Peter Maydell
2020-01-22 13:29   ` Alex Bennée
2020-01-23 12:43   ` Eric Blake [this message]
2020-01-23 14:50     ` Peter Maydell
2020-01-16 14:15 ` [PATCH 2/3] docs: Create stub system manual Peter Maydell
2020-01-21 18:01   ` Peter Maydell
2020-01-22 18:57     ` Alex Bennée
2020-01-23 11:51       ` Peter Maydell
2020-01-16 14:15 ` [PATCH 3/3] qemu-block-drivers: Convert to rST Peter Maydell
2020-01-22 19:00   ` Alex Bennée
2020-01-20 14:26 ` [PATCH 0/3] convert qemu-nbd, qemu-block-drivers " Stefan Hajnoczi

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=c14e6614-4411-e4d1-daab-626e575450fb@redhat.com \
    --to=eblake@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    /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).