qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Lyu Mitnick <mitnick.lyu@gmail.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Kevin Wolf <kwolf@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] GSoC - QCOW2 <-> QED image converter
Date: Wed, 6 Apr 2011 02:03:43 +0800	[thread overview]
Message-ID: <BANLkTim-OHgybKO0xnC_P-1m-J0amupakA@mail.gmail.com> (raw)
In-Reply-To: <BANLkTi=hnMBn__h08ka+V8Rzu6k7ahR64Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1831 bytes --]

Hello Stefan, Kevin

I don't want to diversify my GSoC applications. I thought I should do my
best of
supporting fully VHD and add asynchronous io into block/vpc.c via
coroutines. I
noticed that there is "splitting hard disk images" feature in VHD
specification. I
have take a look of block/raw-win32.c and guess there isn't this feature in
block/vpc.c.
I am wondering whether what I learned is right??

2011/4/5 Stefan Hajnoczi <stefanha@gmail.com>

> On Mon, Apr 4, 2011 at 7:56 PM, Lyu Mitnick <mitnick.lyu@gmail.com> wrote:
> > Hello all,
> > Looking at QEMU'w wiki I saw the "QCOW2 <- > QED image converter", that I
> > am
> > also interested to work as student and apply for GSoC 2011. I have study
> > the
> > specifications of the two images and have some idea about
> > implementation. There
> > is someone already working on this project?? I also want to apply for
> > "Improved
> > image format compatibility". Could I merge the two idea into one
> application
> > or I should
> > apply separately??
>
> Other students have expressed their interest too, but that is normal
> for GSoC project ideas.
>
> Please just note on your application that you'd be interested in doing
> QCOW2<->QED, there's no need to do a separate application in this
> case.  The mentors are the same for both QCOW2<->QED and image format
> updates.  The area of these two projects is similar, and we select the
> most talented students rather than the best application forms.  I am
> confident the selected student(s) would be capable of tackling either
> project.
>
> If you want to diversify your GSoC applications to increase your
> chance of getting a place, then I suggest applying at a different
> organization in addition to QEMU.org.  That way you are not subject to
> the QEMU.org slot allocation.
>
> Stefan
>


Thanks a lot

Mitnick

[-- Attachment #2: Type: text/html, Size: 2523 bytes --]

  reply	other threads:[~2011-04-05 18:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-04 18:56 [Qemu-devel] GSoC - QCOW2 <-> QED image converter Lyu Mitnick
2011-04-05  9:15 ` Stefan Hajnoczi
2011-04-05 18:03   ` Lyu Mitnick [this message]
2011-04-06  6:41     ` Stefan Hajnoczi
2011-04-06 11:13       ` Lyu Mitnick
2011-04-06 12:46         ` Stefan Hajnoczi
2011-04-06 15:06       ` Christoph Hellwig
2011-04-06 15:15         ` Kevin Wolf
2011-04-06 15:52           ` Christoph Hellwig
2011-04-06 23:10             ` Lyu Mitnick
2011-04-11 18:11               ` Christoph Hellwig

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=BANLkTim-OHgybKO0xnC_P-1m-J0amupakA@mail.gmail.com \
    --to=mitnick.lyu@gmail.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    /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).