From: Stefan Hajnoczi <stefanha@redhat.com>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: [PATCH v2 0/3] trace: convert docs to rST and feature "log" backend in quickstart
Date: Wed, 16 Dec 2020 16:09:20 +0000 [thread overview]
Message-ID: <20201216160923.722894-1-stefanha@redhat.com> (raw)
v2:
* Simplify quickstart for the "log" trace backend that is enabled by default
[Peter]
* Don't show ./configure --enable-trace-backends=log example since it's built
by default (changed to --enable-trace-backends=simple,dtrace) [Peter]
Convert tracing.txt to rST and add it to the generated developer documentation.
Peter Maydell suggested making the "log" backend the recommended backend in the
quickstart documentation. It's easier to use than the "simple" backend. The
final patch updates the documentation to do this.
Stefan Hajnoczi (3):
trace: fix simpletrace doc mismerge
tracing: convert documentation to rST
trace: recommend "log" backend for getting started with tracing
docs/devel/index.rst | 1 +
docs/devel/{tracing.txt => tracing.rst} | 185 ++++++++++++++----------
2 files changed, 107 insertions(+), 79 deletions(-)
rename docs/devel/{tracing.txt => tracing.rst} (84%)
--
2.29.2
next reply other threads:[~2020-12-16 16:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-16 16:09 Stefan Hajnoczi [this message]
2020-12-16 16:09 ` [PATCH v2 1/3] trace: fix simpletrace doc mismerge Stefan Hajnoczi
2020-12-16 16:09 ` [PATCH v2 2/3] tracing: convert documentation to rST Stefan Hajnoczi
2021-01-12 14:52 ` Alex Bennée
2020-12-16 16:09 ` [PATCH v2 3/3] trace: recommend "log" backend for getting started with tracing Stefan Hajnoczi
2020-12-31 14:57 ` Peter Maydell
2020-12-31 20:36 ` BALATON Zoltan via
2021-01-12 17:00 ` Stefan Hajnoczi
2021-01-12 14:06 ` [PATCH v2 0/3] trace: convert docs to rST and feature "log" backend in quickstart Stefan Hajnoczi
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=20201216160923.722894-1-stefanha@redhat.com \
--to=stefanha@redhat.com \
--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).