From: Paolo Bonzini <pbonzini@redhat.com>
To: Markus Armbruster <armbru@redhat.com>, qemu-devel@nongnu.org
Cc: libvir-list@redhat.com,
"Peter Maydell" <peter.maydell@linaro.org>,
"John Snow" <jsnow@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>
Subject: Re: A brief look at deprecating our JSON extensions over RFC 8259
Date: Mon, 22 Feb 2021 18:42:00 +0100 [thread overview]
Message-ID: <ceb5d0f8-3022-e91a-006b-5ac6e5862e4a@redhat.com> (raw)
In-Reply-To: <875z2knoa5.fsf@dusky.pond.sub.org>
On 22/02/21 15:57, Markus Armbruster wrote:
> * The block layer's pseudo-protocol "json:" (which can get embedded in
> image headers)
If it gets embedded in image headers, I don't think we'll be able to
deprecate it ever. We'd need to keep a converter for old images, at
which point it's simpler to keep the extensions.
Paolo
next prev parent reply other threads:[~2021-02-22 17:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-22 14:57 A brief look at deprecating our JSON extensions over RFC 8259 Markus Armbruster
2021-02-22 15:10 ` Peter Krempa
2021-02-22 15:24 ` Daniel P. Berrangé
2021-02-22 15:43 ` Liviu Ionescu
2021-02-22 17:47 ` Paolo Bonzini
2021-02-22 17:54 ` Daniel P. Berrangé
2021-02-22 18:06 ` Paolo Bonzini
2021-02-23 9:31 ` Markus Armbruster
2021-02-23 9:37 ` Markus Armbruster
2021-02-23 11:03 ` Peter Maydell
2021-02-23 12:43 ` Markus Armbruster
2021-02-23 9:06 ` Markus Armbruster
2021-02-23 10:59 ` Paolo Bonzini
2021-02-23 12:34 ` Markus Armbruster
2021-02-22 17:42 ` Paolo Bonzini [this message]
2021-02-22 18:01 ` Daniel P. Berrangé
2021-02-22 18:22 ` Peter Krempa
2021-02-22 18:25 ` Peter Krempa
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=ceb5d0f8-3022-e91a-006b-5ac6e5862e4a@redhat.com \
--to=pbonzini@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=jsnow@redhat.com \
--cc=libvir-list@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).