From: Jan Kiszka <jan.kiszka@siemens.com>
To: Sasha Levin <levinsasha928@gmail.com>
Cc: swoop3r@gmx.de, Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] tap: Add optional parameters to up/down script
Date: Thu, 29 Sep 2011 16:10:30 +0200 [thread overview]
Message-ID: <4E847C56.4020701@siemens.com> (raw)
In-Reply-To: <1317304660-18072-1-git-send-email-levinsasha928@gmail.com>
On 2011-09-29 15:57, Sasha Levin wrote:
> This allows the user to add custom parameters to the up or down
> scripts.
>
What kind of parameters would you want to pass? Something that tells VMs
apart (which can be solved without these extensions) or more?
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2011-09-29 14:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-29 13:57 [Qemu-devel] [PATCH] tap: Add optional parameters to up/down script Sasha Levin
2011-09-29 14:10 ` Jan Kiszka [this message]
2011-09-29 14:40 ` Thomas Jung
2011-09-29 15:20 ` Jan Kiszka
2011-09-29 15:39 ` Sasha Levin
2011-09-29 14:53 ` Anthony Liguori
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=4E847C56.4020701@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=aliguori@us.ibm.com \
--cc=levinsasha928@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=swoop3r@gmx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.