All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: Chris Wright <chrisw@redhat.com>,
	qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] Re: KVM call agenda for May 18
Date: Tue, 18 May 2010 09:34:06 -0500	[thread overview]
Message-ID: <4BF2A55E.5030001@codemonkey.ws> (raw)
In-Reply-To: <20100518140927.GJ8328@redhat.com>

On 05/18/2010 09:09 AM, Daniel P. Berrange wrote:
> On Tue, May 18, 2010 at 08:53:19AM -0500, Anthony Liguori wrote:
>    
>> On 05/17/2010 10:23 PM, Chris Wright wrote:
>>      
>>> Please send in any agenda items you are interested in covering.
>>>
>>> If we have a lack of agenda items I'll cancel the week's call.
>>>
>>>        
>> - Slipping 0.13 release out to July 1st.
>>      
> What is the plan wrt QMP and 0.13 ? Is the intention to have 100%[1] of the
> existing monitor commands converted to QMP?

No.  I don't think our goal is to ever fully convert monitor commands to 
QMP.  Some commands simply don't make sense as QMP commands (like x and xp).

Is there a set of commands that you think need to be converted that 
currently aren't?

Regards,

Anthony Liguori

>   There are still quite alot of
> monitor commands not converted and given the time take to get this far, it
> seems optimistic to expect completion by July, let alone a feature freeze
> date preceeding that.
>
> Regards,
> Daniel
>
> [1] Excluding obsolete commands like drive_add, pci_add replaced by device_add
>    


  reply	other threads:[~2010-05-18 14:34 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-18  3:23 KVM call agenda for May 18 Chris Wright
2010-05-18  3:23 ` [Qemu-devel] " Chris Wright
2010-05-18  6:59 ` Brian Jackson
2010-05-18  6:59   ` [Qemu-devel] " Brian Jackson
2010-05-18 13:52   ` Anthony Liguori
2010-05-18 13:52     ` [Qemu-devel] " Anthony Liguori
2010-05-18 19:46     ` Brian Jackson
2010-05-18 19:46       ` [Qemu-devel] " Brian Jackson
2010-05-18 19:51       ` Chris Wright
2010-05-18 19:51         ` [Qemu-devel] " Chris Wright
2010-05-19  8:20     ` Christoph Hellwig
2010-05-19  8:20       ` [Qemu-devel] " Christoph Hellwig
2010-05-19 19:47       ` Anthony Liguori
2010-05-19 19:47         ` [Qemu-devel] " Anthony Liguori
2010-05-25  9:51       ` Avi Kivity
2010-05-25  9:51         ` [Qemu-devel] " Avi Kivity
2010-05-18 13:53 ` Anthony Liguori
2010-05-18 13:53   ` [Qemu-devel] " Anthony Liguori
2010-05-18 14:09   ` Daniel P. Berrange
2010-05-18 14:34     ` Anthony Liguori [this message]
2010-05-18 14:55       ` Daniel P. Berrange
2010-05-18 15:26         ` Anthony Liguori
2010-05-18 15:44         ` Markus Armbruster
2010-05-18 15:44           ` Markus Armbruster
2010-05-18 15:48           ` Markus Armbruster
2010-05-18 15:48             ` Markus Armbruster
2010-05-18 16:00         ` Luiz Capitulino
2010-05-18 16:00           ` Luiz Capitulino
2010-05-18 16:16           ` Daniel P. Berrange
2010-05-18 16:16             ` Daniel P. Berrange
2010-05-18 16:25             ` Anthony Liguori
2010-05-18 16:25               ` Anthony Liguori
2010-05-18 17:46             ` Luiz Capitulino
2010-05-18 17:46               ` Luiz Capitulino
2010-05-18 17:31       ` Avi Kivity
2010-05-18 17:31         ` Avi Kivity
2010-05-18 21:50         ` Anthony Liguori
2010-05-18 21:50           ` Anthony Liguori

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=4BF2A55E.5030001@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=berrange@redhat.com \
    --cc=chrisw@redhat.com \
    --cc=kvm@vger.kernel.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 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.