From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Gleb Natapov <gleb@qumranet.com>
Subject: Re: [Qemu-devel] [PATCH v6 4/8] Use libuuid if available.
Date: Thu, 11 Sep 2008 15:05:00 +0100 [thread overview]
Message-ID: <200809111505.01111.paul@codesourcery.com> (raw)
In-Reply-To: <20080911132411.22719.18188.stgit@gleb-debian.qumranet.com.qumranet.com>
On Thursday 11 September 2008, Gleb Natapov wrote:
> If libuuid is available use it for UUID generation in case a user asks for
> it.
I don't think this feature is worth the extra dependency. IMHO Generation of
UUIDs should be left to the management utility. Anyone invoking qemu manually
can trivially generate a UUID using commonly available tools (e.g. uuidgen).
If we really must have this feature then you need to document it.
Paul
next prev parent reply other threads:[~2008-09-11 14:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-11 13:23 [Qemu-devel] [PATCH v6 0/8] Add new firmware configuration mechanism Gleb Natapov
2008-09-11 13:23 ` [Qemu-devel] [PATCH v6 1/8] Key/value based qemu<->guest firmware communication mechanism Gleb Natapov
2008-09-11 13:24 ` [Qemu-devel] [PATCH v6 2/8] Add -uuid command line option Gleb Natapov
2008-09-11 13:24 ` [Qemu-devel] [PATCH v6 3/8] Add "info uuid" command to monitor Gleb Natapov
2008-09-11 13:24 ` [Qemu-devel] [PATCH v6 4/8] Use libuuid if available Gleb Natapov
2008-09-11 14:05 ` Paul Brook [this message]
2008-09-12 10:13 ` Gleb Natapov
2008-09-11 13:24 ` [Qemu-devel] [PATCH v6 5/8] Add UUID to firmware configuration info Gleb Natapov
2008-09-11 13:24 ` [Qemu-devel] [PATCH v6 6/8] Pass cpu speed into SM BIOS Gleb Natapov
2008-09-11 13:24 ` [Qemu-devel] [PATCH v6 7/8] Add common keys to firmware configuration Gleb Natapov
2008-09-11 13:24 ` [Qemu-devel] [PATCH v6 8/8] Add sparc " Gleb Natapov
2008-09-11 19:30 ` [Qemu-devel] [PATCH v6 0/8] Add new firmware configuration mechanism Blue Swirl
2008-09-16 13:27 ` Gleb Natapov
2008-09-16 17:37 ` Blue Swirl
2008-09-18 18:36 ` Blue Swirl
2008-09-19 10:49 ` Gleb Natapov
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=200809111505.01111.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=gleb@qumranet.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 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.