From: Peter Maydell <peter.maydell@linaro.org>
To: Richard Henderson <richard.henderson@linaro.org>
Cc: "QEMU Developers" <qemu-devel@nongnu.org>,
"Bastian Koppelmann" <kbastian@mail.uni-paderborn.de>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>
Subject: Re: [Qemu-devel] [PATCH 2/5] decodetree: Move documentation to docs/decodetree.rst
Date: Sun, 24 Feb 2019 10:37:04 +0000 [thread overview]
Message-ID: <CAFEAcA_A3cZ4Pv7YT3qzM+krwW+Z6R=oyKcRfuJvr6q5pZj2HA@mail.gmail.com> (raw)
In-Reply-To: <20190223232954.7185-3-richard.henderson@linaro.org>
On Sat, 23 Feb 2019 at 23:35, Richard Henderson
<richard.henderson@linaro.org> wrote:
>
> One great big block comment isn't the best way to document
> the syntax of a language.
>
> Signed-off-by: Richard Henderson <richard.henderson@linaro.org>
> ---
> MAINTAINERS | 1 +
> docs/decodetree.rst | 156 ++++++++++++++++++++++++++++++++++++++++++
> scripts/decodetree.py | 134 +-----------------------------------
> 3 files changed, 158 insertions(+), 133 deletions(-)
> create mode 100644 docs/decodetree.rst
Could you put this in docs/devel/, please ?
Our plan for documentation is to try to split it into
multiple manuals, each of which gets a subdirectory of
docs/, and eventually have nothing still in the docs/
directory itself. This doc should definitely be in
devel/ as it's relevant only to QEMU developers.
thanks
-- PMM
next prev parent reply other threads:[~2019-02-24 10:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-23 23:29 [Qemu-devel] [PATCH 0/5] decodetree enhancements Richard Henderson
2019-02-23 23:29 ` [Qemu-devel] [PATCH 1/5] MAINTAINERS: Add scripts/decodetree.py to the TCG section Richard Henderson
2019-02-23 23:29 ` [Qemu-devel] [PATCH 2/5] decodetree: Move documentation to docs/decodetree.rst Richard Henderson
2019-02-24 10:37 ` Peter Maydell [this message]
2019-02-25 10:06 ` Bastian Koppelmann
2019-02-23 23:29 ` [Qemu-devel] [PATCH 3/5] decodetree: Ensure build_tree does not include values outside insnmask Richard Henderson
2019-02-25 10:08 ` Bastian Koppelmann
2019-02-23 23:29 ` [Qemu-devel] [PATCH 4/5] decodetree: Do not unconditionaly return from Pattern.output_code Richard Henderson
2019-02-23 23:43 ` Philippe Mathieu-Daudé
2019-02-25 10:13 ` Bastian Koppelmann
2019-02-23 23:29 ` [Qemu-devel] [PATCH 5/5] decodetree: Allow grouping of overlapping patterns Richard Henderson
2019-02-23 23:55 ` Philippe Mathieu-Daudé
2019-02-26 9:41 ` Bastian Koppelmann
2019-02-27 12:02 ` [Qemu-devel] [PATCH] test/decode: Add tests for PatternGroups Bastian Koppelmann
2019-02-27 23:04 ` Richard Henderson
2019-02-23 23:29 ` [Qemu-devel] [RFC 6/7] target/hppa: Use pattern groups to decode OR Richard Henderson
2019-02-23 23:29 ` [Qemu-devel] [RFC 7/7] target/riscv: Use pattern groups for RVC Richard Henderson
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_A3cZ4Pv7YT3qzM+krwW+Z6R=oyKcRfuJvr6q5pZj2HA@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=f4bug@amsat.org \
--cc=kbastian@mail.uni-paderborn.de \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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.