From: Paolo Bonzini <pbonzini@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH v2] vl: deprecate -writeconfig
Date: Thu, 25 Feb 2021 15:08:03 +0100 [thread overview]
Message-ID: <7593fccc-fb5b-4e1c-a35f-e9e4ff940a9a@redhat.com> (raw)
In-Reply-To: <YDeuOYpYZX+49AAd@redhat.com>
On 25/02/21 15:03, Daniel P. Berrangé wrote:
> FWIW, we've rarely kept exactly to our 2 cycle plan. In practice it has
> become more of a minimum bar, rather than an exact deadline. If you want
> to promise death in 6.2 though I'll defer to your judgement :=)
>
> Reviewed-by: Daniel P. Berrangé<berrange@redhat.com>
Well, I have patches waiting for the removal and sitting over them for a
year is already enough. :)
Paolo
next prev parent reply other threads:[~2021-02-25 14:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-25 13:13 [PATCH v2] vl: deprecate -writeconfig Paolo Bonzini
2021-02-25 13:18 ` no-reply
2021-02-25 14:03 ` Daniel P. Berrangé
2021-02-25 14:08 ` Paolo Bonzini [this message]
2021-02-25 14:28 ` Markus Armbruster
2021-02-25 14:42 ` Paolo Bonzini
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=7593fccc-fb5b-4e1c-a35f-e9e4ff940a9a@redhat.com \
--to=pbonzini@redhat.com \
--cc=berrange@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 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).