qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: qemu-devel@nongnu.org
Cc: richard.henderson@linaro.org
Subject: [PULL 00/17] QAPI patches patches for 2023-04-28
Date: Fri, 28 Apr 2023 12:28:44 +0200	[thread overview]
Message-ID: <20230428102901.1685375-1-armbru@redhat.com> (raw)

The following changes since commit cc5ee50fff9dbac0aac32cd892a7163c7babcca1:

  Merge tag 'pull-testing-docs-270423-1' of https://gitlab.com/stsquad/qemu into staging (2023-04-27 16:46:17 +0100)

are available in the Git repository at:

  https://repo.or.cz/qemu/armbru.git tags/pull-qapi-2023-04-28

for you to fetch changes up to e2e9e567f0e23971cac35ba1dee7edb51085b5f7:

  docs/devel/qapi-code-gen: Describe some doc markup pitfalls (2023-04-28 11:48:34 +0200)

----------------------------------------------------------------
QAPI patches patches for 2023-04-28

----------------------------------------------------------------
Markus Armbruster (17):
      qga/qapi-schema: Tidy up documentation of guest-fsfreeze-status
      qga/qapi-schema: Fix a misspelled reference
      qapi: Fix misspelled references
      qapi: Fix up references to long gone error classes
      qapi/block-core: Clean up after removal of dirty bitmap @status
      qapi: @foo should be used to reference, not ``foo``
      qapi: Tidy up examples
      qapi: Delete largely misleading "Stability Considerations"
      qapi: Fix bullet list markup in documentation
      qapi: Fix unintended definition lists in documentation
      qga/qapi-schema: Fix member documentation markup
      qapi: Fix argument documentation markup
      qapi: Replace ad hoc "since" documentation by member documentation
      qapi: Fix misspelled section tags in doc comments
      qapi: Format since information the conventional way: (since X.Y)
      qapi storage-daemon/qapi: Fix documentation section structure
      docs/devel/qapi-code-gen: Describe some doc markup pitfalls

 docs/devel/qapi-code-gen.rst         | 62 +++++++++++++++++++++++++--
 docs/interop/firmware.json           |  6 +--
 qapi/block-core.json                 | 82 ++++++++++++++++++------------------
 qapi/block-export.json               |  7 +--
 qapi/block.json                      |  2 +-
 qapi/char.json                       |  4 +-
 qapi/control.json                    |  2 +-
 qapi/cryptodev.json                  |  4 ++
 qapi/job.json                        |  4 +-
 qapi/machine-target.json             |  2 +-
 qapi/machine.json                    | 30 +++++++------
 qapi/migration.json                  | 37 ++++++++++------
 qapi/misc.json                       | 13 +++---
 qapi/net.json                        | 27 +++++-------
 qapi/qapi-schema.json                | 24 +----------
 qapi/qdev.json                       |  2 +-
 qapi/qom.json                        |  4 +-
 qapi/rdma.json                       |  2 +-
 qapi/replay.json                     |  3 ++
 qapi/run-state.json                  | 11 +++--
 qapi/stats.json                      |  3 +-
 qapi/tpm.json                        |  3 +-
 qapi/trace.json                      |  1 +
 qapi/ui.json                         | 12 +++---
 qapi/yank.json                       | 21 ++++-----
 qga/qapi-schema.json                 | 10 ++---
 storage-daemon/qapi/qapi-schema.json | 22 +++++++---
 27 files changed, 231 insertions(+), 169 deletions(-)

-- 
2.39.2



             reply	other threads:[~2023-04-28 10:29 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-28 10:28 Markus Armbruster [this message]
2023-04-28 10:28 ` [PULL 01/17] qga/qapi-schema: Tidy up documentation of guest-fsfreeze-status Markus Armbruster
2023-04-28 10:28 ` [PULL 02/17] qga/qapi-schema: Fix a misspelled reference Markus Armbruster
2023-04-28 10:28 ` [PULL 03/17] qapi: Fix misspelled references Markus Armbruster
2023-04-28 10:28 ` [PULL 04/17] qapi: Fix up references to long gone error classes Markus Armbruster
2023-04-28 10:28 ` [PULL 05/17] qapi/block-core: Clean up after removal of dirty bitmap @status Markus Armbruster
2023-04-28 10:28 ` [PULL 06/17] qapi: @foo should be used to reference, not ``foo`` Markus Armbruster
2023-04-28 10:28 ` [PULL 07/17] qapi: Tidy up examples Markus Armbruster
2023-04-28 10:28 ` [PULL 08/17] qapi: Delete largely misleading "Stability Considerations" Markus Armbruster
2023-04-28 10:28 ` [PULL 09/17] qapi: Fix bullet list markup in documentation Markus Armbruster
2023-04-28 10:28 ` [PULL 10/17] qapi: Fix unintended definition lists " Markus Armbruster
2023-04-28 10:28 ` [PULL 11/17] qga/qapi-schema: Fix member documentation markup Markus Armbruster
2023-04-28 10:28 ` [PULL 12/17] qapi: Fix argument " Markus Armbruster
2023-04-28 10:28 ` [PULL 13/17] qapi: Replace ad hoc "since" documentation by member documentation Markus Armbruster
2023-04-28 10:28 ` [PULL 14/17] qapi: Fix misspelled section tags in doc comments Markus Armbruster
2023-04-28 10:28 ` [PULL 15/17] qapi: Format since information the conventional way: (since X.Y) Markus Armbruster
2023-04-28 10:29 ` [PULL 16/17] qapi storage-daemon/qapi: Fix documentation section structure Markus Armbruster
2023-04-28 10:29 ` [PULL 17/17] docs/devel/qapi-code-gen: Describe some doc markup pitfalls Markus Armbruster
2023-04-29  9:04 ` [PULL 00/17] QAPI patches patches for 2023-04-28 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=20230428102901.1685375-1-armbru@redhat.com \
    --to=armbru@redhat.com \
    --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 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).