From: Kevin Wolf <kwolf@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Programmingkid <programmingkidx@gmail.com>,
qemu-devel qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v3] ui/cocoa.m: Machine menu patch for Mac OS X
Date: Tue, 17 Feb 2015 10:57:22 +0100 [thread overview]
Message-ID: <20150217095722.GC4213@noname.str.redhat.com> (raw)
In-Reply-To: <CAFEAcA9c7ZhN7SaCq1MCEiOP9FbBB6uoedaOGE3+qFqvadAEyQ@mail.gmail.com>
Am 17.02.2015 um 10:41 hat Peter Maydell geschrieben:
> On 17 February 2015 at 18:07, Kevin Wolf <kwolf@redhat.com> wrote:
> > The ID is user-defined, so no, no assumption about it is safe. If you
> > like, you can name your floppy drive 'ide0-cd1', your virtio harddisk
> > 'floppy1' and your ATAPI CD-ROM drive 'virtio0'. But if you do that,
> > I think it's reasonable to argue that it's your own fault that you get
> > misleading menu entries. The default would yield the right results
> > anyway.
>
> Probably wise to have the menu entry include the id string as
> well as any guessed friendly name (or just the id string in cases
> where we can't come up with a guess).
Yes, that's a good suggestion.
Kevin
next prev parent reply other threads:[~2015-02-17 9:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-14 1:43 [Qemu-devel] [PATCH v3] ui/cocoa.m: Machine menu patch for Mac OS X Programmingkid
2015-02-14 2:28 ` Peter Maydell
2015-02-16 10:08 ` Kevin Wolf
[not found] ` <4A70459E-56F8-4360-A795-D9ABED95324D@gmail.com>
[not found] ` <20150216154254.GJ4079@noname.str.redhat.com>
2015-02-16 16:12 ` Programmingkid
2015-02-16 16:22 ` Kevin Wolf
2015-02-16 17:00 ` Programmingkid
2015-02-17 9:07 ` Kevin Wolf
2015-02-17 9:41 ` Peter Maydell
2015-02-17 9:57 ` Kevin Wolf [this message]
2015-02-17 15:52 ` Programmingkid
2015-02-17 12:41 ` Markus Armbruster
2015-02-16 23:41 ` Peter Maydell
2015-02-17 1:55 ` Programmingkid
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=20150217095722.GC4213@noname.str.redhat.com \
--to=kwolf@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=programmingkidx@gmail.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).