WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [PATCH] xm info

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] xm info
From: aq <aquynh@xxxxxxxxx>
Date: Sun, 3 Jul 2005 21:30:46 +0900
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Sun, 03 Jul 2005 12:29:34 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=l8p1L1wcVsVPayzQ+Xy6+nzci0UOHuvfKvruby9ZNW+FJKDC0YU3MUCy+V21pOfqB61FO4Tp786U0z8P/kq9e3d0FCkKzydGlu29L7quzoAiua05dFSPu+NhzBO0dN3tJjP0kg5xRVv5nCP34Vzr8I+rzMoQ0DZurHd+HcGknjo=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <beffde07d3317cff5686f10a29aefd15@xxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <9cde8bff050703001311e0e36b@xxxxxxxxxxxxxx> <c3157a566ff5ee8b4ce9c1ee0093cfe6@xxxxxxxxxxxx> <9cde8bff05070301352470b3f9@xxxxxxxxxxxxxx> <cff5d25b83287c1dd5a5a166fb513e62@xxxxxxxxxxxx> <9cde8bff05070301493e141ab@xxxxxxxxxxxxxx> <beffde07d3317cff5686f10a29aefd15@xxxxxxxxxxxx>
Reply-to: aq <aquynh@xxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On 7/3/05, Keir Fraser <Keir.Fraser@xxxxxxxxxxxx> wrote:
> 
> On 3 Jul 2005, at 09:49, aq wrote:
> 
> >> Yes: that's the only change you made in the file, except for a
> >> one-line
> >> change for xen_extraversion_t.
> >
> > i always think that code inside a switch() should be indented. that is
> > a standard coding style, no?
> 
> The code is indented, of course, as it is already -- but neither Xen
> nor Linux indent the braces enclosing switch or case statements, and
> then indent the code one tab more.

ok, so please unindent that part.

regards,
aq

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel