qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Adam Litke <agl@us.ibm.com>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: jan.kiszka@siemens.com, aliguori@us.ibm.com,
	qemu-devel@nongnu.org, kvm@vger.kernel.org, agraf@suse.de
Subject: Re: [Qemu-devel] Ideas wiki for GSoC 2010
Date: Fri, 12 Mar 2010 09:38:47 -0600	[thread overview]
Message-ID: <1268408327.3287.10.camel@aglitke> (raw)
In-Reply-To: <20100312122241.5cf41093@redhat.com>

On Fri, 2010-03-12 at 12:22 -0300, Luiz Capitulino wrote:
> On Fri, 12 Mar 2010 09:11:31 -0600
> Adam Litke <agl@us.ibm.com> wrote:
> 
> > Hi Luiz.  Around the time when I introduced the new Asynchronous monitor
> > command API we had talked about converting all commands to use this new
> > API so that we can cut down on duplicate code paths and confusing code.
> > I would like to propose this as a GSoC project idea.  Do you think it
> > should stand as its own project or should we merge it into your "Convert
> > Monitor commands to the QObject API" project?
> 
>  I think it's a project by itself, but I wonder if it's too easy/short
> for GSoC. An experienced programmer can do the conversion plus testing
> in a day or two. There are probably a number of cleanups and adaptions
> that can take more, but still seems too short.

So given the relatively small scope of this additional work, maybe it
should be an additional "stretch" goal to be added to your project.
Once the student(s) have gone through the trouble to familiarize
themselves with the monitor code, they would be well-positioned to
complete this extra bit.  How difficult do you imagine it will be to
convert the remaining commands over to QObject?

-- 
Thanks,
Adam

  reply	other threads:[~2010-03-12 15:39 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-10 21:30 [Qemu-devel] Ideas wiki for GSoC 2010 Luiz Capitulino
2010-03-11  7:55 ` [Qemu-devel] " Avi Kivity
2010-03-11  9:43   ` Paolo Bonzini
2010-03-11 11:25     ` Alexander Graf
2010-03-11 11:54       ` Avi Kivity
2010-03-11 11:56         ` Alexander Graf
2010-03-11 11:58           ` Avi Kivity
2010-03-11 12:03             ` Alexander Graf
2010-03-11 12:15               ` Avi Kivity
2010-03-12 10:49                 ` [Qemu-devel] Re: [Android-virt] " Christoffer Dall
2010-03-12 12:32                   ` Luiz Capitulino
2010-03-11 19:06               ` [Qemu-devel] " Cam Macdonell
2010-03-11 12:09       ` Paolo Bonzini
2010-03-11 13:19         ` Luiz Capitulino
2010-03-13  3:13           ` Edgar E. Iglesias
2010-03-11 13:16       ` Luiz Capitulino
2010-03-12 10:47       ` Jes Sorensen
2010-03-11 12:59     ` Luiz Capitulino
2010-03-11 13:00       ` Alexander Graf
2010-03-11 13:21         ` Luiz Capitulino
2010-03-11 22:59   ` Jamie Lokier
2010-03-12  9:48     ` Paolo Bonzini
2010-03-12  9:59       ` Gleb Natapov
2010-03-11 12:26 ` Avi Kivity
2010-03-11 13:09 ` [Qemu-devel] " Lucas Meneghel Rodrigues
2010-03-12 15:11 ` Adam Litke
2010-03-12 15:22   ` Luiz Capitulino
2010-03-12 15:38     ` Adam Litke [this message]
2010-03-12 15:56       ` Luiz Capitulino
2010-03-12 16:36         ` Anthony Liguori
2010-03-12 17:35           ` Luiz Capitulino
2010-03-15 12:25 ` Avi Kivity
2010-03-15 12:38   ` Joerg Roedel
2010-03-15 12:42     ` Avi Kivity
2010-03-15 13:14       ` Anthony Liguori
2010-03-15 15:59         ` Joerg Roedel
2010-03-15 12:53   ` Muli Ben-Yehuda
2010-03-15 13:03     ` Joerg Roedel
2010-03-15 13:11       ` Avi Kivity
2010-03-15 13:23         ` Anthony Liguori
2010-03-15 15:06           ` Avi Kivity
2010-03-16  1:21             ` Anthony Liguori
2010-03-16  5:50               ` Avi Kivity
2010-03-15 13:24         ` Joerg Roedel
2010-03-15 13:55           ` Anthony Liguori
2010-03-15 14:18       ` Muli Ben-Yehuda

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=1268408327.3287.10.camel@aglitke \
    --to=agl@us.ibm.com \
    --cc=agraf@suse.de \
    --cc=aliguori@us.ibm.com \
    --cc=jan.kiszka@siemens.com \
    --cc=kvm@vger.kernel.org \
    --cc=lcapitulino@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).