On Wed, 26 Feb 2020 at 07:50, Markus Armbruster wrote:
> Peter Maydell writes:
> > * get the qapidoc generation conversion reviewed and into
> >master (since at the moment it outputs into files included
> >from qemu-doc)
>
> Not true. QAPI doc comments go into *separate* manuals, the "Q
Peter Maydell writes:
> On Tue, 25 Feb 2020 at 17:48, Paolo Bonzini wrote:
>>
>> On 25/02/20 18:11, Peter Maydell wrote:
>> >> I assume these are not meant to be applied now, except patch 2?
>> > No, I intended them to be reviewable and applied now. Why
>> > do you think we should wait?
>>
>> Be
On Tue, 25 Feb 2020 at 20:10, Paolo Bonzini wrote:
> The main issue with this series and Kashyap's is that if we don't manage to
> get
> everything done in 5.0 we have a mutilated qemu-doc. Then either we keep it
> mutilated or we scramble to undo the work. So I would agree to commit the
> series
Il mar 25 feb 2020, 20:50 Peter Maydell ha
scritto:
> On Tue, 25 Feb 2020 at 19:10, Paolo Bonzini wrote:
> I feel like we're working a bit at cross purposes here so maybe
> we'd benefit from just nailing down who's going to do what and
> in which order?
>
I am not going to do much more than wha
On Tue, 25 Feb 2020 at 19:10, Paolo Bonzini wrote:
> This could go in independently. It would make Kashyap's series
> conflict, but I have already rebased it on top.
I'm happy to collect up 'docs' patches for pullreqs (and fix up
conflicts etc as they arise) if that helps in getting things into
t
Il mar 25 feb 2020, 19:57 Peter Maydell ha
scritto:
> > The QAPI docs are in other manuals in docs/interop/, aren't they?
>
> Yes, but until we complete the conversion we can't get
> rid of the qemu-doc.html output, because that's where the
> HTML output from the QAPI doc generation goes.
>
Righ
On Tue, 25 Feb 2020 at 18:28, Paolo Bonzini wrote:
>
> On 25/02/20 18:59, Peter Maydell wrote:
> > My assumption was that we would attack this by:
> > * converting chunks of the documentation which are in qemu-doc.texi
> >but which aren't in the qemu.1 manpage (basically in the way this
> >
On 25/02/20 18:59, Peter Maydell wrote:
> My assumption was that we would attack this by:
> * converting chunks of the documentation which are in qemu-doc.texi
>but which aren't in the qemu.1 manpage (basically in the way this
>series is doing)
> * get the qapidoc generation conversion re
On Tue, 25 Feb 2020 at 17:48, Paolo Bonzini wrote:
>
> On 25/02/20 18:11, Peter Maydell wrote:
> >> I assume these are not meant to be applied now, except patch 2?
> > No, I intended them to be reviewable and applied now. Why
> > do you think we should wait?
>
> Because they remove information fro
On 25/02/20 18:11, Peter Maydell wrote:
>> I assume these are not meant to be applied now, except patch 2?
> No, I intended them to be reviewable and applied now. Why
> do you think we should wait?
Because they remove information from qemu-doc.texi. I think it's
feasible to do a mass conversion q
On Tue, 25 Feb 2020 at 17:01, Paolo Bonzini wrote:
>
> On 25/02/20 16:41, Peter Maydell wrote:
> > This patchset converts some texi files used in qemu-doc.texi to rST:
> >
> > * docs/security.texi
> > * qemu-tech.texi
> > * qemu-deprecated.texi
> >
> > which all end up as sections of the "syste
On 25/02/20 16:41, Peter Maydell wrote:
> This patchset converts some texi files used in qemu-doc.texi to rST:
>
> * docs/security.texi
> * qemu-tech.texi
> * qemu-deprecated.texi
>
> which all end up as sections of the "system" manual.
>
> In all cases, these pieces of the documentation are
This patchset converts some texi files used in qemu-doc.texi to rST:
* docs/security.texi
* qemu-tech.texi
* qemu-deprecated.texi
which all end up as sections of the "system" manual.
In all cases, these pieces of the documentation are part of
the qemu-doc HTML file, but not included in the qe
13 matches
Mail list logo
