From: Gleb Natapov <gleb@qumranet.com>
To: Chris Lalancette <clalance@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH 0/3]: Add UUID command-line option
Date: Mon, 28 Jul 2008 17:15:15 +0300 [thread overview]
Message-ID: <20080728141515.GJ3196@minantech.com> (raw)
In-Reply-To: <488DC8B2.1070009@redhat.com>
Hi Chris,
On Mon, Jul 28, 2008 at 03:25:06PM +0200, Chris Lalancette wrote:
> All,
> Attached is a three part patch series to implement a "-uuid" command-line
> option to qemu. The original work for this was all done by Gleb Natapov; since
> there hadn't seemed to be any activity on this since June, I picked up his
> patches and ran with them (original posting:
> http://www.archivum.info/qemu-devel@nongnu.org/2008-06/msg00167.html). These
> patches are basically the same as his, just cleaned up according to Anthony
> Liguori's feedback.
Actually there was activity on this. I addressed Anthony's feedback and
reposted the patch series (I think even twice). Here is the last one:
http://lists.gnu.org/archive/html/qemu-devel/2008-06/msg00448.html
http://lists.gnu.org/archive/html/qemu-devel/2008-06/msg00442.html
http://lists.gnu.org/archive/html/qemu-devel/2008-06/msg00443.html
http://lists.gnu.org/archive/html/qemu-devel/2008-06/msg00444.html
http://lists.gnu.org/archive/html/qemu-devel/2008-06/msg00445.html
http://lists.gnu.org/archive/html/qemu-devel/2008-06/msg00446.html
Fabrice said that he doesn't like vmware backdoor interface though
(http://lists.gnu.org/archive/html/qemu-devel/2008-06/msg00487.html)
I asked what interface he wants to use for qemu/guest communication, but
he never replied to this :(
I also want to see those patches going in I don't care much who will
push them. I can resent last series one more time if it will help.
--
Gleb.
next prev parent reply other threads:[~2008-07-28 14:15 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-28 13:25 [Qemu-devel] [PATCH 0/3]: Add UUID command-line option Chris Lalancette
2008-07-28 14:15 ` Gleb Natapov [this message]
2008-07-28 14:37 ` [Qemu-devel] " Anthony Liguori
2008-07-28 14:41 ` Chris Lalancette
2008-07-28 15:02 ` Anthony Liguori
2008-07-28 15:09 ` Chris Lalancette
2008-07-28 15:12 ` Anthony Liguori
2008-07-28 15:42 ` Chris Lalancette
2008-07-28 16:02 ` Gleb Natapov
2008-07-28 16:17 ` Anthony Liguori
2008-07-28 16:27 ` Gleb Natapov
2008-07-28 17:41 ` Blue Swirl
2008-07-28 16:28 ` Jamie Lokier
2008-07-28 19:02 ` Anthony Liguori
2008-07-28 20:00 ` Jamie Lokier
2008-07-28 20:25 ` Anthony Liguori
2008-07-28 20:40 ` Paul Brook
2008-07-28 20:55 ` Anthony Liguori
2008-07-29 6:31 ` Gleb Natapov
2008-07-28 15:48 ` Jamie Lokier
2008-07-31 19:45 ` [Qemu-devel] " Sebastian Herbszt
2008-07-28 15:49 ` [Qemu-devel] " Jamie Lokier
2008-07-28 16:06 ` Anthony Liguori
2008-07-28 15:35 ` Gleb Natapov
2008-07-29 19:22 ` Anthony Liguori
2008-07-29 19:50 ` Gleb Natapov
2008-07-30 17:32 ` Blue Swirl
2008-08-05 14:33 ` Gleb Natapov
2008-08-06 2:35 ` Anthony Liguori
2008-08-06 16:26 ` Blue Swirl
2008-08-06 16:33 ` Anthony Liguori
2008-08-06 22:07 ` [Qemu-devel] " Sebastian Herbszt
2008-08-06 22:11 ` [Qemu-devel] " Anthony Liguori
2008-07-29 8:15 ` Daniel P. Berrange
2008-07-29 8:42 ` Chris Lalancette
2008-07-28 15:51 ` Jamie Lokier
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=20080728141515.GJ3196@minantech.com \
--to=gleb@qumranet.com \
--cc=clalance@redhat.com \
--cc=qemu-devel@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).