qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Luiz Capitulino <lcapitulino@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Anthony Liguori <aliguori@linux.vnet.ibm.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 5/7] QMP: Update spec file
Date: Fri, 18 Dec 2009 16:08:14 -0200	[thread overview]
Message-ID: <20091218160814.29aced99@doriath> (raw)
In-Reply-To: <m3tyvo88dh.fsf@crossbow.pond.sub.org>

On Fri, 18 Dec 2009 19:06:18 +0100
Markus Armbruster <armbru@redhat.com> wrote:

> Anthony Liguori <aliguori@linux.vnet.ibm.com> writes:
> 
> > Markus Armbruster wrote:
> >> While I think these promises are appropriate for a mature version of the
> >> protocol, I do not think we should make them for 0.12.
> >>
> >> We've just dreamed up version 0.1 of the protocol.  It hasn't been used
> >> in anger.  Yes, we put some serious thought in it, and we even have
> >> prototype code using it in libvirt, but let's face it, we're not
> >> infallible: we *will* have to evolve stuff.
> >>
> >> Without a real user, there is no real need to constrict evolution of the
> >> protocol in such a harsh way.  All it'll buy is is compatibility cruft.
> >> Passage of time will bring us plenty of cruft without us setting
> >> ourselves up for extras.
> >>
> >> Let's cut ourselves some slack here, please.
> >>   
> >
> > I've been working on the release notes and I was intending on
> > announcing the QMP support in 0.12 as a "preview" with full support in
> > 0.13.
> >
> > The idea being that we would try to maintain compatibility but
> > "preview" gives us enough slack that if we break it, we can at least
> > claim that it was just a preview ;-)
> 
> Works for me.  But then the unconditional promise in this patch is
> misleading.  If we care, we should amend it to spell out "this is
> preview, all promises are null and void".

 I'd prefer to just drop this part.

  reply	other threads:[~2009-12-18 18:08 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-18 15:24 [Qemu-devel] [FOR 0.12 0/7]: More QMP related fixes Luiz Capitulino
2009-12-18 15:24 ` [Qemu-devel] [PATCH 1/7] QMP: Only handle converted commands Luiz Capitulino
2009-12-18 15:25 ` [Qemu-devel] [PATCH 2/7] QMP: Return an empty dict by default Luiz Capitulino
2009-12-18 15:25 ` [Qemu-devel] [PATCH 3/7] QMP: Assure that returned data is a QDict Luiz Capitulino
2009-12-21 19:21   ` Nathan Baum
2009-12-22  3:06     ` Luiz Capitulino
2009-12-18 15:25 ` [Qemu-devel] [PATCH 4/7] QMP: Update README file Luiz Capitulino
2009-12-18 15:25 ` [Qemu-devel] [PATCH 5/7] QMP: Update spec file Luiz Capitulino
2009-12-18 17:20   ` Markus Armbruster
2009-12-18 17:44     ` Anthony Liguori
2009-12-18 17:48       ` Luiz Capitulino
2009-12-18 18:06       ` Markus Armbruster
2009-12-18 18:08         ` Luiz Capitulino [this message]
2009-12-18 17:55     ` Luiz Capitulino
2009-12-18 18:38       ` Markus Armbruster
2009-12-18 15:25 ` [Qemu-devel] [PATCH 6/7] monitor: Introduce 'M' argument type Luiz Capitulino
2009-12-18 15:25 ` [Qemu-devel] [PATCH 7/7] monitor: do_balloon(): Use " Luiz Capitulino
2009-12-18 17:25 ` [Qemu-devel] [FOR 0.12 0/7]: More QMP related fixes Markus Armbruster

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=20091218160814.29aced99@doriath \
    --to=lcapitulino@redhat.com \
    --cc=aliguori@linux.vnet.ibm.com \
    --cc=armbru@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).