qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: John Snow <jsnow@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Daniel Berrange <berrange@redhat.com>,
	qemu-devel@nongnu.org
Subject: Re: [PATCH 6/6] docs/devel: create "Miscellaneous Topics" subsection
Date: Thu, 05 Aug 2021 13:12:23 +0100	[thread overview]
Message-ID: <877dh0ks24.fsf@linaro.org> (raw)
In-Reply-To: <20210804005621.1577302-7-jsnow@redhat.com>


John Snow <jsnow@redhat.com> writes:

> The hallmark of any truly great taxonomical reorganization: the bin of
> leftover bits and pieces that didn't neatly fit elsewhere.
>
> Signed-off-by: John Snow <jsnow@redhat.com>
> ---
>  docs/devel/index.rst        |  9 +--------
>  docs/devel/section-misc.rst | 15 +++++++++++++++
>  2 files changed, 16 insertions(+), 8 deletions(-)
>  create mode 100644 docs/devel/section-misc.rst
>
> diff --git a/docs/devel/index.rst b/docs/devel/index.rst
> index da579a7b666..ef14f3302e1 100644
> --- a/docs/devel/index.rst
> +++ b/docs/devel/index.rst
> @@ -14,11 +14,4 @@ modifying QEMU's source code.
>     section-testing-debugging
>     section-tcg
>     section-subsystems
> -   control-flow-integrity
> -   decodetree

decodetree is TCG as per Peter's comment

> -   s390-dasd-ipl
> -   qom

I feel as though QOM should be in the Developing QEMU section as it's a
fairly core part of the programming experience. Maybe?

Anyway it's an improvement:

Reviewed-by: Alex Bennée <alex.bennee@linaro.org>

-- 
Alex Bennée


  reply	other threads:[~2021-08-05 12:14 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-04  0:56 [PATCH 0/6] docs/devel: Organize devel manual into further subsections John Snow
2021-08-04  0:56 ` [PATCH 1/6] docs/devel: create "Community & Governance" subsection John Snow
2021-08-05 11:53   ` Alex Bennée
2021-08-04  0:56 ` [PATCH 2/6] docs/devel: create "Developing QEMU" subsection John Snow
2021-08-05 11:53   ` Alex Bennée
2021-08-04  0:56 ` [PATCH 3/6] docs/devel: create "Testing & Debugging" subsection John Snow
2021-08-05 12:08   ` Alex Bennée
2021-08-04  0:56 ` [PATCH 4/6] docs/devel: create TCG subsection John Snow
2021-08-05 12:09   ` Alex Bennée
2021-08-05 15:20     ` John Snow
2021-08-04  0:56 ` [PATCH 5/6] docs/devel: create "Subsystem APIs" subsection John Snow
2021-08-05 12:10   ` Alex Bennée
2021-08-04  0:56 ` [PATCH 6/6] docs/devel: create "Miscellaneous Topics" subsection John Snow
2021-08-05 12:12   ` Alex Bennée [this message]
2021-08-05 15:26     ` John Snow
2021-08-05  9:40 ` [PATCH 0/6] docs/devel: Organize devel manual into further subsections Peter Maydell

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=877dh0ks24.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=berrange@redhat.com \
    --cc=jsnow@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).