From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Xen-devel <xen-devel@lists.xen.org>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>
Subject: [PATCH 0/2] docs: Improve coverage docs
Date: Wed, 3 Apr 2019 15:59:58 +0100 [thread overview]
Message-ID: <1554303600-27933-1-git-send-email-andrew.cooper3@citrix.com> (raw)
This was identified IRL at the safety summit, so I took the opportunity to
improve things.
The result of this series, and some other in-development bits, can be found
at:
https://andrewcoop-xen.readthedocs.io/en/docs-devel/index.html
Andrew Cooper (2):
docs/sphinx: Introduce a hypervisor guide section
docs/hypervisor-guide: Code Coverage
docs/hypervisor-guide/code-coverage.rst | 102 ++++++++++++++++++++++++++
docs/hypervisor-guide/index.rst | 7 ++
docs/index.rst | 18 +++++
docs/misc/coverage.pandoc | 124 --------------------------------
4 files changed, 127 insertions(+), 124 deletions(-)
create mode 100644 docs/hypervisor-guide/code-coverage.rst
create mode 100644 docs/hypervisor-guide/index.rst
delete mode 100644 docs/misc/coverage.pandoc
--
2.1.4
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next reply other threads:[~2019-04-03 14:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-03 14:59 Andrew Cooper [this message]
2019-04-03 14:59 ` [PATCH 1/2] docs/sphinx: Introduce a hypervisor guide section Andrew Cooper
2019-04-04 12:10 ` Wei Liu
2019-04-03 15:00 ` [PATCH 2/2] docs/hypervisor-guide: Code Coverage Andrew Cooper
2019-04-04 12:07 ` Artem Mygaiev
2019-04-04 12:29 ` Julien Grall
2019-04-04 12:46 ` Andrew Cooper
2019-04-04 13:26 ` Julien Grall
2019-04-04 12:10 ` Wei Liu
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=1554303600-27933-1-git-send-email-andrew.cooper3@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.