From: Pekka Enberg <penberg@kernel.org>
To: walimis <walimisdev@gmail.com>
Cc: Sasha Levin <levinsasha928@gmail.com>,
kvm@vger.kernel.org, mingo@elte.hu, asias.hejun@gmail.com,
gorcunov@gmail.com
Subject: Re: [PATCH 1/7] kvm tools: Print version when running 'kvm --version'
Date: Fri, 12 Aug 2011 18:39:46 +0300 (EEST) [thread overview]
Message-ID: <alpine.DEB.2.00.1108121839140.6873@tiger> (raw)
In-Reply-To: <20110812152240.GA20279@walimis-desktop>
On Fri, 12 Aug 2011, walimis wrote:
>> @@ -24,6 +24,7 @@ struct cmd_struct kvm_commands[] = {
>> { "balloon", kvm_cmd_balloon, NULL, 0 },
>> { "list", kvm_cmd_list, NULL, 0 },
>> { "version", kvm_cmd_version, NULL, 0 },
>> + { "--version", kvm_cmd_version, NULL, 0 },
> Although it works, I think it's not good way to implement a option
> as a command.
Well, I already merged the patch because the whole series was so
super-cool. What downsides are there to implementing the alias like this?
Pekka
next prev parent reply other threads:[~2011-08-12 15:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-12 15:20 [PATCH 1/7] kvm tools: Print version when running 'kvm --version' Sasha Levin
2011-08-12 15:20 ` [PATCH 2/7] kvm tools: Connect existing command helpers to 'kvm help' Sasha Levin
2011-08-12 15:20 ` [PATCH 3/7] kvm tools: Improve 'kvm stop' parameters Sasha Levin
2011-08-12 15:20 ` [PATCH 4/7] kvm tools: Improve 'kvm resume' parameters Sasha Levin
2011-08-12 15:20 ` [PATCH 5/7] kvm tools: Improve 'kvm pause' parameters Sasha Levin
2011-08-12 15:20 ` [PATCH 6/7] kvm tools: Improve 'kvm debug' parameters Sasha Levin
2011-08-12 15:21 ` [PATCH 7/7] kvm tools: Improve 'kvm balloon' parameters Sasha Levin
2011-08-12 15:22 ` [PATCH 1/7] kvm tools: Print version when running 'kvm --version' walimis
2011-08-12 15:39 ` Pekka Enberg [this message]
2011-08-12 15:43 ` walimis
2011-08-12 15:47 ` Sasha Levin
2011-08-12 15:45 ` walimis
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=alpine.DEB.2.00.1108121839140.6873@tiger \
--to=penberg@kernel.org \
--cc=asias.hejun@gmail.com \
--cc=gorcunov@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=levinsasha928@gmail.com \
--cc=mingo@elte.hu \
--cc=walimisdev@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox