Re: [PATCH v3 31/33] docs: Stop building qemu-doc

2020-03-12 Thread Markus Armbruster
Peter Maydell writes: > On Thu, 12 Mar 2020 at 06:06, Markus Armbruster wrote: >> Would it be possible to additionally render a complete manual as one >> humongous .html? Without an index, there's only search, and the >> ergonomics of searching within a single page are so much better. > > There

Re: [PATCH v3 31/33] docs: Stop building qemu-doc

2020-03-12 Thread Peter Maydell
On Thu, 12 Mar 2020 at 06:06, Markus Armbruster wrote: > Would it be possible to additionally render a complete manual as one > humongous .html? Without an index, there's only search, and the > ergonomics of searching within a single page are so much better. There is a "build one big fat HTML pa

Re: [PATCH v3 31/33] docs: Stop building qemu-doc

2020-03-11 Thread Markus Armbruster
Peter Maydell writes: > On Wed, 11 Mar 2020 at 14:53, Markus Armbruster wrote: >> This appears to lose plain text, PDF and info output. Any chance to get >> plain text back? > > This is deliberate. Consensus when we decided on the docs > transition plan was that plain text was not a useful outp

Re: [PATCH v3 31/33] docs: Stop building qemu-doc

2020-03-11 Thread Peter Maydell
On Wed, 11 Mar 2020 at 15:22, Paolo Bonzini wrote: > Also, man to text is obviously doable with groff if we're content with the > man page content. The manpages are a small subset of the full HTML manual, though (as was also the case for the texinfo generation process). thanks -- PMM

Re: [PATCH v3 31/33] docs: Stop building qemu-doc

2020-03-11 Thread Paolo Bonzini
Also, man to text is obviously doable with groff if we're content with the man page content. Paolo Il mer 11 mar 2020, 16:16 Peter Maydell ha scritto: > On Wed, 11 Mar 2020 at 14:53, Markus Armbruster wrote: > > This appears to lose plain text, PDF and info output. Any chance to get > > plain

Re: [PATCH v3 31/33] docs: Stop building qemu-doc

2020-03-11 Thread Peter Maydell
On Wed, 11 Mar 2020 at 14:53, Markus Armbruster wrote: > This appears to lose plain text, PDF and info output. Any chance to get > plain text back? This is deliberate. Consensus when we decided on the docs transition plan was that plain text was not a useful output format. (discussed in https://

Re: [PATCH v3 31/33] docs: Stop building qemu-doc

2020-03-11 Thread Markus Armbruster
Peter Maydell writes: > Stop building the old texinfo qemu-doc; all its contents are > now available in the Sphinx-generated manuals and manpages. > > Signed-off-by: Peter Maydell This appears to lose plain text, PDF and info output. Any chance to get plain text back?

Re: [PATCH v3 31/33] docs: Stop building qemu-doc

2020-03-02 Thread Alex Bennée
Peter Maydell writes: > Stop building the old texinfo qemu-doc; all its contents are > now available in the Sphinx-generated manuals and manpages. > > Signed-off-by: Peter Maydell Reviewed-by: Alex Bennée -- Alex Bennée

[PATCH v3 31/33] docs: Stop building qemu-doc

2020-02-28 Thread Peter Maydell
Stop building the old texinfo qemu-doc; all its contents are now available in the Sphinx-generated manuals and manpages. Signed-off-by: Peter Maydell --- docs/specs/ivshmem-spec.txt | 4 ++-- Makefile| 39 - .gitignore |