From: Jeff Dike <jdike@karaya.com>
To: Daniel Phillips <phillips@bonn-fries.net>,
William Lee Irwin III <wli@holomorphy.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: UML has been sent to Linus
Date: Fri, 28 Dec 2001 23:49:38 -0500 [thread overview]
Message-ID: <200112290449.XAA08848@ccure.karaya.com> (raw)
In-Reply-To: Your message of "Sat, 29 Dec 2001 01:24:25 +0100." <E16K7IZ-0000BL-00@starship.berlin>
phillips@bonn-fries.net said:
> There are interesting applications we'll start to see when UML is
> more widely available, such as simulation of clusters, or 'Linux
> Bubbles' under Windows.
Yeah, there are a ton of interesting possibilities which I have probably not
done enough to publicize.
> I think you've done a great job maintaining UML out-of-tree
Thanks!
> for more than a year, with very little assistance,
UML is approaching three years old (I started hacking in Feb 1998;
the first public sign of it was the following June).
> and I hope you won't have to shoulder that extra burden much longer.
Yeah, one can hope :-)
I'm currently banging on bugs and residual missing functionality. When I
think that's all done, that will be what I call UML V1.0 and I will send
it to Marcelo. At that point, the out-of-tree phase of UML will be over.
wli@holomorphy.com said:
> uml has been a very valuable tool for me to both learn kernel
> programming
That's why I originally wrote it...
> and to get kernel programming done. And it's extremely
> cool.
> IMHO it's excellent programming as well.
Thanks, thanks, and thanks!
Jeff
next prev parent reply other threads:[~2001-12-29 3:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-28 6:35 UML has been sent to Linus Jeff Dike
2001-12-29 0:24 ` Daniel Phillips
2001-12-29 4:49 ` Jeff Dike [this message]
2001-12-29 0:29 ` William Lee Irwin III
[not found] <20011228101647.GB20899@h55p111.delphi.afb.lu.se>
2001-12-28 18:31 ` Jeff Dike
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=200112290449.XAA08848@ccure.karaya.com \
--to=jdike@karaya.com \
--cc=linux-kernel@vger.kernel.org \
--cc=phillips@bonn-fries.net \
--cc=wli@holomorphy.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