All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pierre Morel <pmorel@linux.ibm.com>
To: Cornelia Huck <cohuck@redhat.com>,
	Peter Maydell <peter.maydell@linaro.org>
Cc: Tony Krowiak <akrowiak@linux.ibm.com>,
	"Jason J . Herne" <jjherne@linux.ibm.com>,
	Thomas Huth <thuth@redhat.com>,
	QEMU Developers <qemu-devel@nongnu.org>,
	Halil Pasic <pasic@linux.ibm.com>,
	Christian Borntraeger <borntraeger@de.ibm.com>,
	qemu-s390x <qemu-s390x@nongnu.org>
Subject: Re: [PATCH v2 2/2] docs: rstfy vfio-ap documentation
Date: Tue, 18 Feb 2020 14:57:31 +0100	[thread overview]
Message-ID: <73579e24-3a2f-e4d1-2fd8-3470e5aec694@linux.ibm.com> (raw)
In-Reply-To: <20200218134451.23c77b1f.cohuck@redhat.com>



On 2020-02-18 13:44, Cornelia Huck wrote:
> On Thu, 13 Feb 2020 18:54:37 +0000
> Peter Maydell <peter.maydell@linaro.org> wrote:
> 
>> On Thu, 13 Feb 2020 at 18:38, Pierre Morel <pmorel@linux.ibm.com>
>> wrote:> However it may be because I do not use the right tools.
>>> Did not find which one I am suppose to use.
>>> Currently using:
>>> rst2latex vfio-ap.rst > vfio-ap.tex && pdflatex vfio-ap.tex
>>
>> The only supported way to build the docs is with Sphinx.
>>
>> Option 1:
>>
>> If you have the right versions of the tools installed
>> then running "make" in the usual way will build HTML docs
>> into the docs/ subdirectory of your build directory.
>> Passing --enable-docs to configure will cause it to complain
>> if you're missing a tool rather than silently not building
>> the docs. This is what we expect most users to be doing.
>>
>> Option 2:
>>
>> You can run Sphinx 'manually' with something like
>>   sphinx-build docs /tmp/sphinx-out
>> which will build a single big fat manual into the
>> specified output directory (here /tmp/sphinx-out).
>> This option is provided mostly so that sites like
>> 'readthedocs' can produce the documentation without having
>> to run our Makefiles.
>>
>> PDF is not an officially supported (by us) output format,
>> but if you really want it you can generate it with
>>   sphinx-build -b latex docs /tmp/sphinx-out
>>   cd /tmp/sphinx-out
>>   make
>> which will generate a QEMU.pdf in /tmp/sphinx-out.
>>
>> We're unlikely to want to make tweaks to the documentation
>> sources to fix infelicities in the formatting of the PDF,
>> though.
> 
> FWIW, using option 2 to produce a pdf seems to end up with something
> decent-looking with these patches applied. (Lots of warnings from
> LaTex, but that seems preexisting.)
> 

OK, then I effectively did not use the right tools. Sorry for this and 
thanks for having leaning again.

For the content I was OK with all so:
Reviewed-by: Pierre Morel <pmorel@linux.ibm.com>

and thanks for the work.




-- 
Pierre Morel
IBM Lab Boeblingen



  reply	other threads:[~2020-02-18 13:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-13 16:29 [PATCH v2 0/2] docs: rstfy some s390 docs Cornelia Huck
2020-02-13 16:29 ` [PATCH v2 1/2] docs: rstfy s390 dasd ipl documentation Cornelia Huck
2020-02-13 16:29 ` [PATCH v2 2/2] docs: rstfy vfio-ap documentation Cornelia Huck
2020-02-13 18:38   ` Pierre Morel
2020-02-13 18:54     ` Peter Maydell
2020-02-18 12:44       ` Cornelia Huck
2020-02-18 13:57         ` Pierre Morel [this message]
2020-02-18 13:05 ` [PATCH v2 0/2] docs: rstfy some s390 docs Cornelia Huck
2020-02-21  8:24 ` Cornelia Huck

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=73579e24-3a2f-e4d1-2fd8-3470e5aec694@linux.ibm.com \
    --to=pmorel@linux.ibm.com \
    --cc=akrowiak@linux.ibm.com \
    --cc=borntraeger@de.ibm.com \
    --cc=cohuck@redhat.com \
    --cc=jjherne@linux.ibm.com \
    --cc=pasic@linux.ibm.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-s390x@nongnu.org \
    --cc=thuth@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.