From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Add support for a configuration file
Date: Thu, 15 May 2008 10:05:21 -0500 [thread overview]
Message-ID: <482C5131.40100@codemonkey.ws> (raw)
In-Reply-To: <20080515220340.10e3fa92.mle+tools@mega-nerd.com>
Erik de Castro Lopo wrote:
> Anthony Liguori wrote:
>
>
>> There has been an awful lot of discussion about a configuration file with
>> almost no general agreement except that one is strongly desired.
>>
>
> One thing I'd like to see is the ability to include one config file
> inside another.
>
The astute reader will notice that my patch already includes that
functionality :-)
Regards,
Anthony Liguori
> The use case for this is to have something like:
>
> my-machine-base.conf
>
> which contains base configuration stuff. I might then have a couple
> of other configs which include the above file:
>
> my-machine-use-vde-networking.conf
> my-machine-standard-networking.conf
>
> The base config might not even be a valid config by itself, but is
> only useful when included with one of these other configs.
>
> Comments?
>
> Cheers,
> Erik
>
next prev parent reply other threads:[~2008-05-15 15:05 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-13 21:19 [Qemu-devel] [PATCH] Add support for a configuration file Anthony Liguori
2008-05-13 23:07 ` [Qemu-devel] " Anthony Liguori
2008-05-13 23:20 ` [Qemu-devel] Re: [kvm-devel] " Daniel P. Berrange
2008-05-14 6:35 ` Colin Adams
2008-05-14 14:41 ` Avi Kivity
2008-05-14 14:52 ` Dor Laor
2008-05-14 15:02 ` Daniel P. Berrange
2008-05-14 15:18 ` [kvm-devel] [Qemu-devel] " Anthony Liguori
2008-05-14 14:59 ` [Qemu-devel] Re: [kvm-devel] " Anthony Liguori
2008-05-14 15:10 ` Andreas Färber
2008-05-15 14:50 ` Ian Jackson
2008-05-14 8:27 ` [Qemu-devel] " Fabrice Bellard
2008-05-14 10:31 ` Avi Kivity
2008-05-14 12:26 ` Fabrice Bellard
2008-05-14 13:31 ` [kvm-devel] " Daniel P. Berrange
2008-05-15 8:04 ` Avi Kivity
2008-05-15 11:52 ` Daniel P. Berrange
2008-05-15 12:04 ` Avi Kivity
2008-05-15 12:16 ` Andreas Färber
2008-05-15 12:20 ` Laurent Vivier
2008-05-14 14:06 ` Anthony Liguori
2008-05-14 14:26 ` Paul Brook
2008-05-14 14:45 ` [kvm-devel] " Javier Guerra
2008-05-14 15:13 ` Johannes Schindelin
2008-05-14 15:30 ` Javier Guerra
2008-05-14 15:37 ` Johannes Schindelin
2008-05-14 15:42 ` Javier Guerra
2008-05-14 16:07 ` Kelly French
2008-05-15 14:59 ` Paul Brook
2008-05-14 16:01 ` Andreas Färber
2008-05-14 16:21 ` Daniel P. Berrange
2008-05-14 16:37 ` Andreas Färber
2008-05-14 16:29 ` Fabrice Bellard
2008-05-17 21:49 ` Luca Barbato
2008-05-14 15:22 ` Daniel P. Berrange
2008-05-14 15:09 ` Anthony Liguori
2008-05-14 15:18 ` Paul Brook
2008-05-14 16:25 ` Fabrice Bellard
2008-05-14 14:36 ` andrzej zaborowski
2008-05-14 15:10 ` Johannes Schindelin
2008-05-15 14:58 ` Ian Jackson
2008-05-15 12:03 ` [Qemu-devel] " Erik de Castro Lopo
2008-05-15 12:36 ` andrzej zaborowski
2008-05-15 13:22 ` Daniel P. Berrange
2008-05-15 14:46 ` andrzej zaborowski
2008-05-15 15:05 ` Anthony Liguori [this message]
2008-05-15 15:26 ` Avi Kivity
2008-05-15 18:50 ` 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=482C5131.40100@codemonkey.ws \
--to=anthony@codemonkey.ws \
--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).