All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org, eblake@redhat.com, jsnow@redhat.com
Subject: Re: [PATCH v2] qapi: Consistently use x.y with since
Date: Tue, 3 Nov 2026 08:09:21 +0000	[thread overview]
Message-ID: <aumWsYlcoRRv35Oh@redhat.com> (raw)
In-Reply-To: <20261103073311.3501327-1-armbru@redhat.com>

On Tue, Nov 03, 2026 at 08:33:11AM +0100, Markus Armbruster wrote:
> docs/devel/qapi-code-gen.rst documents "Since: x.y.z" and "(since
> x.y.z)", but we almost always use just x.y.  Makes sense, because .z
> is exclusively for stable branches, where we generally don't mess with
> QAPI schemas.
> 
> Adjust the doc and the exceptions to the ruling practice.  Do not
> touch versions prior to 3.0.0, because .z was not for stable branches
> back then.
> 
> Signed-off-by: Markus Armbruster <armbru@redhat.com>
> ---
> v2: Don't change versions prior to 3.0.0, and improve commit message
>     [Daniel]
> 
>  docs/devel/qapi-code-gen.rst | 4 ++--
>  docs/interop/firmware.json   | 4 ++--
>  qapi/accelerator.json        | 6 +++---
>  qapi/crypto.json             | 2 +-
>  4 files changed, 8 insertions(+), 8 deletions(-)

Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>


With regards,
Daniel
-- 
|: https://berrange.com       ~~        https://hachyderm.io/@berrange :|
|: https://libvirt.org          ~~          https://entangle-photo.org :|
|: https://pixelfed.art/berrange   ~~    https://fstop138.berrange.com :|



      reply	other threads:[~2026-11-03  8:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-03  7:33 [PATCH v2] qapi: Consistently use x.y with since Markus Armbruster
2026-11-03  8:09 ` Daniel P. Berrangé [this message]

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=aumWsYlcoRRv35Oh@redhat.com \
    --to=berrange@redhat.com \
    --cc=armbru@redhat.com \
    --cc=eblake@redhat.com \
    --cc=jsnow@redhat.com \
    --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 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.