From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Eduardo Habkost <ehabkost@redhat.com>,
Gabriel Barreto <sbarreto.gabriel@gmail.com>,
QEMU Developers <qemu-devel@nongnu.org>,
"Emilio G. Cota" <cota@braap.org>,
Stefan Hajnoczi <stefanha@redhat.com>,
Cleber Rosa <crosa@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>, John Snow <jsnow@redhat.com>
Subject: Re: [Qemu-devel] Introducing GSoC project: API Documentation Generation
Date: Tue, 21 May 2019 12:06:00 +0100 [thread overview]
Message-ID: <20190521110600.GJ25835@redhat.com> (raw)
In-Reply-To: <CAFEAcA8bs0M4Ofdq1tt8uZvWHK49PNRFz3SQhxEHT_uPGmBHOQ@mail.gmail.com>
On Tue, May 21, 2019 at 10:43:04AM +0100, Peter Maydell wrote:
> On Tue, 21 May 2019 at 09:54, Daniel P. Berrangé <berrange@redhat.com> wrote:
> > Hawkmoth seems pretty attractive in its output format, but doesn't appear
> > to be part of either Debian or Fedora distros, so we would have to bundle
> > it in QEMU I expect. My big concern there is that there have only been
> > 2 contributors to Hawkmoth in its entire 3 year existance, which makes
> > me fear for its long term viability if the main author gives up.
>
> The dependency on clang 6 and the python bindings to it might also
> be awkward for bundling it with QEMU...
Requiring a second C compiler to build docs is rather unappealing :-(
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2019-05-21 11:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-20 18:41 [Qemu-devel] Introducing GSoC project: API Documentation Generation Eduardo Habkost
2019-05-20 18:48 ` John Snow
2019-05-21 8:53 ` Daniel P. Berrangé
2019-05-21 9:43 ` Peter Maydell
2019-05-21 11:06 ` Daniel P. Berrangé [this message]
2019-05-21 10:55 ` Paolo Bonzini
2019-05-21 15:18 ` Markus Armbruster
2019-05-21 15:25 ` Daniel P. Berrangé
2019-05-21 15:27 ` Peter Maydell
2019-05-21 17:14 ` Paolo Bonzini
2019-05-21 20:32 ` John Snow
2019-05-21 20:37 ` Eduardo Habkost
2019-05-22 8:20 ` Paolo Bonzini
2019-05-23 12:20 ` John Snow
2019-05-24 18:34 ` Paolo Bonzini
2019-05-24 19:08 ` Eduardo Habkost
2019-05-24 20:02 ` Paolo Bonzini
2019-05-21 16:17 ` Eduardo Habkost
2019-05-21 17:14 ` Paolo Bonzini
2019-05-21 9:42 ` Peter Maydell
2019-05-21 11:01 ` Paolo Bonzini
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=20190521110600.GJ25835@redhat.com \
--to=berrange@redhat.com \
--cc=cota@braap.org \
--cc=crosa@redhat.com \
--cc=ehabkost@redhat.com \
--cc=jsnow@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=sbarreto.gabriel@gmail.com \
--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).