From: Rusty Russell <rusty@rustcorp.com.au>
To: Andi Kleen <ak@suse.de>
Cc: Virtualization Mailing List <virtualization@lists.osdl.org>,
Andrew Morton <akpm@osdl.org>, Chris Wright <chrisw@sous-sol.org>
Subject: Re: Paravirt-ops VMI / Xen / lrustyvisor merge status
Date: Fri, 09 Feb 2007 19:46:14 +1100 [thread overview]
Message-ID: <1171010774.2718.23.camel@localhost.localdomain> (raw)
In-Reply-To: <200702090835.04666.ak@suse.de>
On Fri, 2007-02-09 at 08:35 +0100, Andi Kleen wrote:
> > I'm just doing the final file moving now (everything in
> > arch/i386/lguest), expect to send out something within 48 hours (I need
> > to sync up to latest git tree, too).
>
> Hmm, how much baking did it get yet outside rustylabs? Has it been much
> externally tested at all?
Judging from the bug reports, I have some users 8)
> Also I don't think there hasn't been any review yet. Perhaps it's a little
> late now.
We'll see. It's pretty self-contained, though.
Rusty.
next prev parent reply other threads:[~2007-02-09 8:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-09 5:28 Paravirt-ops VMI / Xen / lrustyvisor merge status Zachary Amsden
2007-02-09 5:54 ` Rusty Russell
2007-02-09 6:12 ` Zachary Amsden
2007-02-09 6:24 ` Jeremy Fitzhardinge
2007-02-09 6:58 ` Zachary Amsden
2007-02-09 6:44 ` Rusty Russell
2007-02-09 6:57 ` Jeremy Fitzhardinge
2007-02-09 6:59 ` Zachary Amsden
2007-02-09 7:06 ` Jeremy Fitzhardinge
2007-02-09 7:20 ` Rusty Russell
2007-02-09 7:35 ` Andi Kleen
2007-02-09 8:46 ` Rusty Russell [this message]
2007-02-09 6:10 ` Jeremy Fitzhardinge
2007-02-09 7:21 ` Andi Kleen
2007-02-09 7:35 ` Zachary Amsden
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=1171010774.2718.23.camel@localhost.localdomain \
--to=rusty@rustcorp.com.au \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=chrisw@sous-sol.org \
--cc=virtualization@lists.osdl.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.