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


[Xen-tools] Re: [Xen-devel] [PATCH] rework xen/xm/main.py to be more str

To: Sean Dague <sean@xxxxxxxxx>
Subject: [Xen-tools] Re: [Xen-devel] [PATCH] rework xen/xm/main.py to be more straight forward
From: Mark Williamson <mark.williamson@xxxxxxxxxxxx>
Date: Fri, 5 Aug 2005 17:14:13 +0100
Cc: xen-tools@xxxxxxxxxxxxxxxxxxx, Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>
Delivery-date: Fri, 05 Aug 2005 16:14:24 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20050805155735.GE11062@xxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-tools-request@lists.xensource.com?subject=help>
List-id: Xen control tools developers <xen-tools.lists.xensource.com>
List-post: <mailto:xen-tools@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-tools>, <mailto:xen-tools-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-tools>, <mailto:xen-tools-request@lists.xensource.com?subject=unsubscribe>
References: <20050801192216.GA5974@xxxxxxxxxxxxxxxxxxx> <200508051636.51634.mark.williamson@xxxxxxxxxxxx> <20050805155735.GE11062@xxxxxxxxxxxxxxxxxxx>
Sender: xen-tools-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.8.2
> If abbreviations are specifically called out (not just magically matched)
> I'd not be opposed to it.  But each one should be a two or three letter
> code only, and specifically named in the documentation as well as in the
> code.

I don't think magical matching does any harm for normal use but abbreviations 
should be fine also.  Almost the only things I type these days are "xm li" 
and "xm cre".  It's really not that important compared to getting everything 
else up to speed, so I'm not going to make a fuss over it.


Xen-tools mailing list