Hello Peter,
Peter Maydell writes:
> On Sun, 27 Sep 2020 at 03:21, Maxim Cournoyer
> wrote:
[...]
>> I personally don't understand the rationale of hiding the devel section
>> from users, especially given the kind of users QEMU is likely to attract
>> (e.g, teksavvy people, perhaps themselve
On Sun, 27 Sep 2020 at 03:21, Maxim Cournoyer wrote:
> Peter Maydell writes:
> > It is the best way we found for getting Sphinx to do what we wanted.
> > I agree that it would be nicer to have one manual with all the user
> > facing parts in it, but it is apparently not possible to do that withou
Hello Peter,
Peter Maydell writes:
> On Sat, 26 Sep 2020 at 05:36, Maxim Cournoyer
> wrote:
>> > This isn't the right thing. You should be pointing sphinx-build
>> > at each of the individual manuals (system, interop, etc) and
>> > generating one info file for each. This is because we generate
On Sat, 26 Sep 2020 at 05:36, Maxim Cournoyer wrote:
> > This isn't the right thing. You should be pointing sphinx-build
> > at each of the individual manuals (system, interop, etc) and
> > generating one info file for each. This is because we generate
> > manuals for each of these including the '
Hello Peter,
Peter Maydell writes:
> On Fri, 25 Sep 2020 at 07:27, Maxim Cournoyer
> wrote:
>>
>> Take advantage of the Sphinx texinfo backend to generate a QEMU info
>> manual. The texinfo format allows for more structure and info readers
>> provide more advanced navigation capabilities comp
On Fri, 25 Sep 2020 at 07:27, Maxim Cournoyer wrote:
>
> Take advantage of the Sphinx texinfo backend to generate a QEMU info
> manual. The texinfo format allows for more structure and info readers
> provide more advanced navigation capabilities compared to manpages
> readers.
Not providing an i
Patchew URL:
https://patchew.org/QEMU/20200925024143.26492-1-maxim.courno...@gmail.com/
Hi,
This series failed the docker-mingw@fedora build test. Please find the testing
commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
=== TEST SCRIPT BEG
install the info manual.
=== TEST SCRIPT BEGIN ===
#!/bin/bash
git rev-parse base > /dev/null || exit 0
git config --local diff.renamelimit 0
git config --local diff.renames True
git config --local diff.algorithm histogram
./scripts/checkpatch.pl --mailback base..
=== TEST SCRIPT END ===
Updat
Take advantage of the Sphinx texinfo backend to generate a QEMU info
manual. The texinfo format allows for more structure and info readers
provide more advanced navigation capabilities compared to manpages
readers.
* configure (infodir): Add the --infodir option, which allows
configuring the dire
