This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] xm create option parsing..

To: Mike Wray <mike.wray@xxxxxxxxxx>
Subject: Re: [Xen-devel] xm create option parsing..
From: Ian Pratt <Ian.Pratt@xxxxxxxxxxxx>
Date: Fri, 30 Jul 2004 10:53:08 +0100
Cc: Ian Pratt <Ian.Pratt@xxxxxxxxxxxx>, Steven Hand <Steven.Hand@xxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxxxx, Ian.Pratt@xxxxxxxxxxxx
Delivery-date: Fri, 30 Jul 2004 10:53:08 +0100
Envelope-to: Steven.Hand@xxxxxxxxxxxx
In-reply-to: Your message of "Fri, 30 Jul 2004 10:08:20 BST." <410A1004.2050801@xxxxxxxxxx>
> We potentially have
> xm <xm options> subcommand <subcommand options/args>
> It doesn't really make sense to allow xm options after the subcommand.

What <xm options> do we currently have? Having a -U to set the
host:port might be nice, but what others do we currently have?

> Each subcommand is responsible for parsing its own options, so
> we could get 'xm create' etc. to allow options after the args.
> I'll make the change.

Users will thank you ;-)