From: Jeff Dike <jdike@addtoit.com>
To: "Américo Wang" <xiyou.wangcong@gmail.com>
Cc: Dimitry Golubovsky <golubovsky@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: Current status of UML development?
Date: Fri, 22 Jan 2010 12:11:45 -0500 [thread overview]
Message-ID: <20100122171145.GA13074@c2.user-mode-linux.org> (raw)
In-Reply-To: <20100122162356.GA4771@hack>
On Sat, Jan 23, 2010 at 12:23:56AM +0800, Américo Wang wrote:
> On Thu, Jan 21, 2010 at 03:27:58PM -0500, Dimitry Golubovsky wrote:
> >I am learning/experimenting with UML internals, and am curious what is
> >the current status of its development? Has UML become stable enough so
> >it does not need any improvement (at least for i386), or has its
> >development just ceased in favor of other virtualization techniques?
> >
>
> Of course not.
This is being generous. I haven't really done any work on UML in the
last year or so, although bugs are found and patches contributed (by
Américo, among others).
Jeff
next prev parent reply other threads:[~2010-01-22 17:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-21 20:27 Current status of UML development? Dimitry Golubovsky
2010-01-22 16:23 ` Américo Wang
2010-01-22 17:11 ` Jeff Dike [this message]
2010-01-23 15:37 ` Américo Wang
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=20100122171145.GA13074@c2.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=golubovsky@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xiyou.wangcong@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