"Daniel P. Berrange" writes:
[...]
> The main problem encountered with this patch series is the
> split between argv and config parameters. The qemu-config.c
> file provides the information is a good data format, allowing
> programatic access to the list of parameters for each config
> option (eg
On Mon, 07 Jun 2010 11:07:14 -0500
Anthony Liguori wrote:
> Hi Daniel,
>
> On 06/07/2010 09:42 AM, Daniel P. Berrange wrote:
> > As everyone here agrees, having management apps parse -help output
> > to determine the QEMU capabilities is not at all nice, because it
> > is an ill-defined& fragil
Hi Daniel,
On 06/07/2010 09:42 AM, Daniel P. Berrange wrote:
As everyone here agrees, having management apps parse -help output
to determine the QEMU capabilities is not at all nice, because it
is an ill-defined& fragile data format. Looking more broadly these
same issues apply to all the other
On 06/07/2010 10:10 AM, Daniel P. Berrange wrote:
On Mon, Jun 07, 2010 at 09:58:11AM -0500, Anthony Liguori wrote:
On 06/07/2010 09:42 AM, Daniel P. Berrange wrote:
As everyone here agrees, having management apps parse -help output
to determine the QEMU capabilities is not at all nice
On 06/07/2010 09:42 AM, Daniel P. Berrange wrote:
As everyone here agrees, having management apps parse -help output
to determine the QEMU capabilities is not at all nice, because it
is an ill-defined& fragile data format. Looking more broadly these
same issues apply to all the other command lin
On Mon, Jun 07, 2010 at 09:58:11AM -0500, Anthony Liguori wrote:
> On 06/07/2010 09:42 AM, Daniel P. Berrange wrote:
> >As everyone here agrees, having management apps parse -help output
> >to determine the QEMU capabilities is not at all nice, because it
> >is an ill-defined& fragile data format.
As everyone here agrees, having management apps parse -help output
to determine the QEMU capabilities is not at all nice, because it
is an ill-defined & fragile data format. Looking more broadly these
same issues apply to all the other command line options that accept
a '?' flag for querying capabi