From: Peter Maydell <peter.maydell@linaro.org>
To: John Snow <jsnow@redhat.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
Eduardo Habkost <ehabkost@redhat.com>,
Gabriel Barreto <sbarreto.gabriel@gmail.com>
Subject: Re: [Qemu-devel] GSoC project: API Documentation Generation links and comments
Date: Tue, 3 Sep 2019 09:21:06 +0100 [thread overview]
Message-ID: <CAFEAcA_fZEmsTuHPnUA-KFZLKubrOR-Ggi58HUVKrFSuMx4PSA@mail.gmail.com> (raw)
In-Reply-To: <ca896264-89fc-bcb6-9e21-b411bd4f9a01@redhat.com>
On Tue, 27 Aug 2019 at 22:01, John Snow <jsnow@redhat.com> wrote:
>
>
>
> On 8/27/19 4:56 PM, Peter Maydell wrote:
> > On Tue, 27 Aug 2019 at 21:52, John Snow <jsnow@redhat.com> wrote:
> >> - For theming, I'm a fan of the RTD theme, because I think it makes the
> >> TOC tree stand out better and makes for nicer browsing than the default
> >> alabaster theme. Maybe when there's a better over-arching TOC laid out
> >> with better organization we could see which themes the list likes best.
> >
> > FWIW, for the in-tree doc generation I opted for Alabaster
> > (though I prefer RTD's look as well) because Alabaster doesn't
> > require shipping any fonts, whereas RTD does, and it seemed
> > easier to sidestep any questions about whether a font file in the
> > docs was mere aggregation or not. For "putting docs up on the
>
> What do you mean by "mere aggregation"?
I mean what the GPL means by that term, ie the situation
where you can put a GPL-licensed thing and a non-GPL
licensed thing together without the non-GPL thing falling
under the terms of the GPL. (The canonical example is "Linux
distro CD which contains binaries for lots of different programs".)
thanks
-- PMM
prev parent reply other threads:[~2019-09-03 8:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-26 18:51 [Qemu-devel] GSoC project: API Documentation Generation links and comments Gabriel Barreto
2019-08-27 20:52 ` John Snow
2019-08-27 20:56 ` Peter Maydell
2019-08-27 21:01 ` John Snow
2019-09-03 8:21 ` Peter Maydell [this message]
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=CAFEAcA_fZEmsTuHPnUA-KFZLKubrOR-Ggi58HUVKrFSuMx4PSA@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=ehabkost@redhat.com \
--cc=jsnow@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sbarreto.gabriel@gmail.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).