qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: qemu-devel@nongnu.org, "Peter Maydell" <peter.maydell@linaro.org>,
	"Alex Bennée" <alex.bennee@linaro.org>
Cc: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
	"Fam Zheng" <fam@euphon.net>
Subject: [Qemu-devel] [PATCH 0/3] travis-ci: Test installing Sphinx documentation
Date: Fri,  8 Mar 2019 17:29:03 +0100	[thread overview]
Message-ID: <20190308162906.10491-1-philmd@redhat.com> (raw)

Hi,

This series improve the Travis CI to test installing the Sphinx
generated documentation in in-tree and out-of-tree builds.

It is based on Peter's "Fix various issues with Sphinx build
machinery" series:
https://lists.gnu.org/archive/html/qemu-devel/2019-03/msg02625.html

Regards,

Phil.

Based-on: <20190308135744.6480-1-peter.maydell@linaro.org>

Philippe Mathieu-Daudé (3):
  .travis.yml: Reduce the out-of-tree target list
  .travis.yml: Test the documentation installation process
  .travis.yml: Test installing Sphinx documentation in out-of-tree build

 .travis.yml | 20 +++++++++++++++-----
 1 file changed, 15 insertions(+), 5 deletions(-)

-- 
2.20.1

             reply	other threads:[~2019-03-08 16:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-08 16:29 Philippe Mathieu-Daudé [this message]
2019-03-08 16:29 ` [Qemu-devel] [PATCH 1/3] .travis.yml: Reduce the out-of-tree target list Philippe Mathieu-Daudé
2019-03-08 16:29 ` [Qemu-devel] [PATCH 2/3] .travis.yml: Test the documentation installation process Philippe Mathieu-Daudé
2019-03-08 16:29 ` [Qemu-devel] [PATCH 3/3] .travis.yml: Test installing Sphinx documentation in out-of-tree build Philippe Mathieu-Daudé
2019-03-08 16:55 ` [Qemu-devel] [PATCH 0/3] travis-ci: Test installing Sphinx documentation Alex Bennée

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=20190308162906.10491-1-philmd@redhat.com \
    --to=philmd@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=fam@euphon.net \
    --cc=peter.maydell@linaro.org \
    --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).