public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Besser <thomas.besser@archIT.uni-karlsruhe.de>
To: kvm@vger.kernel.org
Subject: Re: New version of my kvmctl script
Date: Wed, 04 Jun 2008 11:41:57 +0200	[thread overview]
Message-ID: <g25o15$m0h$2@ger.gmane.org> (raw)
In-Reply-To: 200806021137.10184.fjwcash@gmail.com

Freddie Cash wrote:

> On June 2, 2008 11:20 am FinnTux N/A wrote:
>> 2008/6/2 Freddie Cash <fjwcash@gmail.com>:
> Considering this is a test harness and not a control program, perhaps it
> should be renamed in the kvm sources/builds, to something more
> appropriate like kvmtest.
> 
>> Anyways, I was afraid of these naming issues. kvmctl is pretty generic
>> name. Any suggestions?
> 
> I'd prefer to keep the management/control scripts/apps named kvmctl, as
> that's easier to remember and fits with things like sysctl, apachectl,
> brctl, and other similar apps.

Full ACK from me! 

I would also prefer, that 'kvmctl' is really for controlling kvm virtual
machines.

Should we make a bug report to package 'kvm'?

Regards
Thomas


  parent reply	other threads:[~2008-06-04  9:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-02 17:29 New version of my kvmctl script FinnTux N/A
2008-06-02 18:11 ` Freddie Cash
2008-06-02 18:20   ` FinnTux N/A
2008-06-02 18:36     ` FinnTux N/A
2008-06-02 18:37     ` Freddie Cash
2008-06-02 23:02       ` Javier Guerra
2008-06-03 17:05         ` Javier Guerra
2008-06-04  9:41       ` Thomas Besser [this message]
2008-06-04 10:38       ` Avi Kivity
     [not found]     ` <4863A487.5080706@tmr.com>
2008-07-24 19:57       ` FinnTux
2008-09-07 21:41         ` FinnTux
2008-09-07 21:51           ` FinnTux
2008-09-10 14:04             ` Marshal Newrock
2009-01-20 18:20               ` FinnTux
2008-06-04  9:36 ` Thomas Besser

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='g25o15$m0h$2@ger.gmane.org' \
    --to=thomas.besser@archit.uni-karlsruhe.de \
    --cc=kvm@vger.kernel.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