qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gabriel Barreto <sbarreto.gabriel@gmail.com>
To: ehabkost@redhat.com, qemu-devel@nongnu.org
Subject: [Qemu-devel] GSoC project: API Documentation Generation links and comments
Date: Mon, 26 Aug 2019 15:51:33 -0300	[thread overview]
Message-ID: <CAJzA9zP0GnZ17_YSxUhAGFrD_fCM-R=rxEVN5y9V-5-5zTsnVw@mail.gmail.com> (raw)

I've uploaded to my github repository¹ the work done so far. Using
Peter's patches as a starting point, we were able to generate
kernel-docs documentation for some of QEMU's APIs. After studying the
available options, we found a nice solution to publish the
documentation online and keep it updated, using Github Pages and
Travis CI. The idea is to use QEMU's Github mirror, updating the
documentation (located on a gh-pages branch) with every push done to
the master branch. I've implemented this and it's available at a
Github Page² on a gh-pages branch managed by travis jobs. The default
theme needs better structure, but a search in existing documentation
is possible as an out-of-the-box feature. My work is not done yet, as
I still need to rebase my commits to obtain a proper format for RFCs
and figure out a better alternative to deal with the massive number of
warnings that happen when generating the documentation. I'll keep
working on it and welcome any feedback from you. I'm available to
answer all questions you might have.


[1] https://github.com/gsb16/qemu
[2] https://gsb16.github.io/qemu/


Kind Regards,
Gabriel Barreto


             reply	other threads:[~2019-08-26 18:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-26 18:51 Gabriel Barreto [this message]
2019-08-27 20:52 ` [Qemu-devel] GSoC project: API Documentation Generation links and comments John Snow
2019-08-27 20:56   ` Peter Maydell
2019-08-27 21:01     ` John Snow
2019-09-03  8:21       ` Peter Maydell

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='CAJzA9zP0GnZ17_YSxUhAGFrD_fCM-R=rxEVN5y9V-5-5zTsnVw@mail.gmail.com' \
    --to=sbarreto.gabriel@gmail.com \
    --cc=ehabkost@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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).