From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Benjamin Prosnitz <b-prosnitz-angj7XTnwNpXfO9P/gJGhg@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Google Summer of Code
Date: Sun, 04 Mar 2007 10:55:43 +0200 [thread overview]
Message-ID: <45EA898F.2010701@qumranet.com> (raw)
In-Reply-To: <1172934617.23252.2.camel@localhost>
Benjamin Prosnitz wrote:
> Will KVM be participating in Google's Summer of Code?
>
>
Excellent idea. The only snag I see is that it's difficult to what will
be needed for kvm by summer.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
next prev parent reply other threads:[~2007-03-04 8:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-03 15:10 Google Summer of Code Benjamin Prosnitz
2007-03-04 8:55 ` Avi Kivity [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-02-25 19:15 Jacob Thebault-Spieker
2008-02-25 20:36 ` Leon Woestenberg
2008-02-25 20:42 ` Jacob Thebault-Spieker
2008-02-26 0:34 ` Philip Balister
2008-02-26 5:27 ` Jacob Thebault-Spieker
2008-02-26 10:41 ` Paul Sokolovsky
2008-02-25 20:40 ` Jelle de Jong
2008-02-26 0:07 ` Erik Hovland
2013-02-26 13:35 Ognjen Ikovic
2013-04-09 15:21 Thibault, Daniel
[not found] <48CF5AC71E61DB46B70D0F388054EFFD12D0DC32@VAL-E-02.valcartier.drdc-rddc.gc.ca>
2013-04-10 21:53 ` Jérémie Galarneau
[not found] ` <CA+jJMxtP+n274AhsXQ23TXYPo8UsXtShjYxwJwwO69e=N1nbnQ@mail.gmail.com>
2013-04-11 13:20 ` Thibault, Daniel
2016-03-13 12:24 Shreedhar Manek
2017-02-20 5:29 Matthew Sedam
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=45EA898F.2010701@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=b-prosnitz-angj7XTnwNpXfO9P/gJGhg@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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.