From: Eduardo Habkost <ehabkost@redhat.com>
To: Mike Burns <mburns@redhat.com>
Cc: Michael Goldish <mgoldish@redhat.com>,
kvm@vger.kernel.org, Uri Lublin <ulublin@redhat.com>
Subject: Re: [PATCH][KVM-AUTOTEST] Add custom install option for kvm_install
Date: Mon, 11 May 2009 15:34:50 -0300 [thread overview]
Message-ID: <20090511183450.GJ4871@blackpad> (raw)
In-Reply-To: <4A0865D3.7020500@redhat.com>
On Mon, May 11, 2009 at 01:52:19PM -0400, Mike Burns wrote:
> Michael Goldish wrote:
<snip>
>> 2. Why not just pass the parameters via the command line, e.g.
>> install_command = my_script.sh param1 param2
>>
> That would work as well. It could be done either way, but if someone
> wanted to use something other than bash, then this way might be easier.
What is bash-specific about environment variables or command-line args?
Also, exporting the config dictionary as environment variables doesn't
exclude the possibility of simply passing command-line arguments on
install_command, if the user wants to do so. Both methods would work.
--
Eduardo
next prev parent reply other threads:[~2009-05-11 18:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1254147621.368741242063155059.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com>
2009-05-11 17:36 ` [PATCH][KVM-AUTOTEST] Add custom install option for kvm_install Michael Goldish
2009-05-11 17:52 ` Mike Burns
2009-05-11 18:34 ` Eduardo Habkost [this message]
2009-05-11 18:43 ` Mike Burns
2009-05-11 18:30 ` Eduardo Habkost
2009-05-12 15:34 Mike Burns
2009-06-01 15:46 ` Uri Lublin
2009-06-01 18:25 ` Mike Burns
[not found] <471764781.379441242067968821.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com>
2009-05-11 19:00 ` Michael Goldish
2009-05-11 19:19 ` Eduardo Pereira Habkost
2009-05-12 15:28 ` Mike Burns
2009-05-13 7:12 ` Avi Kivity
-- strict thread matches above, loose matches on Subject: below --
2009-05-11 15:51 Mike Burns
2009-05-11 18:52 ` Lucas Meneghel Rodrigues
2009-05-08 18:55 Mike Burns
2009-05-11 13:49 ` Eduardo Habkost
2009-05-11 15:06 ` Mike Burns
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=20090511183450.GJ4871@blackpad \
--to=ehabkost@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mburns@redhat.com \
--cc=mgoldish@redhat.com \
--cc=ulublin@redhat.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