From: Thomas Huth <thuth@redhat.com>
To: Aleksandar Markovic <aleksandar.m.mail@gmail.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [QUESTION] "cpu" vs "core"
Date: Thu, 5 Dec 2019 14:47:51 +0100 [thread overview]
Message-ID: <8a2b8d3e-e933-22b0-1d5d-11e5a5134b6a@redhat.com> (raw)
In-Reply-To: <CAL1e-=hzSLWQ2_qTOXc30FpaMO65uKGqUP9agE+Ti1cfEU9j=A@mail.gmail.com>
On 05/12/2019 14.11, Aleksandar Markovic wrote:
> Hi, all.
>
> Times are changing, and perhaps some words change their significance or
> are less in use.
>
> What do you think of introducing a new option in our command line
> "-core", that would be (code-wise) a sinomym to "-cpu" (that becomes
> almost archaic)?
The QEMU command line is too overcrowded already, so let's please not
add redundant synonyms here. But if you think that -cpu is not clear
enough, I suggest you send some patches to improve the documentation
of that parameter instead.
Cheers,
Thomas
prev parent reply other threads:[~2019-12-05 13:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-05 13:11 [QUESTION] "cpu" vs "core" Aleksandar Markovic
2019-12-05 13:47 ` Thomas Huth [this message]
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=8a2b8d3e-e933-22b0-1d5d-11e5a5134b6a@redhat.com \
--to=thuth@redhat.com \
--cc=aleksandar.m.mail@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).