From: Ted Kaczmarek <tedkaz@optonline.net>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: changeset 6902 update
Date: Sat, 17 Sep 2005 11:22:54 -0400 [thread overview]
Message-ID: <1126970574.3233.68.camel@pluto.linsolutions.com> (raw)
Things are looking great, the handling of failed domU creation is much
better, and even when one fails and sticks around, xm destroy is
cleaning it up. I have only done about 20% of my testing but these where
the show stoppers before.
Kudo's to all you brilliant minds putting this great code together.
Regards,
Ted
next reply other threads:[~2005-09-17 15:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-17 15:22 Ted Kaczmarek [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-09-17 15:23 changeset 6902 update Ted Kaczmarek
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=1126970574.3233.68.camel@pluto.linsolutions.com \
--to=tedkaz@optonline.net \
--cc=xen-devel@lists.xensource.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 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.