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] Add sequence number to 'xm info'

To: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] Add sequence number to 'xm info'
From: Dan Smith <danms@xxxxxxxxxx>
Date: Wed, 28 Sep 2005 17:14:00 -0700
Cc: Xen Developers <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 29 Sep 2005 00:12:18 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <A95E2296287EAD4EB592B5DEEFCE0E9D32E03D@xxxxxxxxxxxxxxxxxxxxxxxxxxx> (Ian Pratt's message of "Thu, 29 Sep 2005 00:03:04 +0100")
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: <A95E2296287EAD4EB592B5DEEFCE0E9D32E03D@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Gnus/5.110003 (No Gnus v0.3) Emacs/21.3 (gnu/linux)
IP> I guess for trees that are direct clones of xenbits with no local
IP> modifications then the short id is meaningful. Such trees are
IP> probably in the majority.  

Indeed.  Additionally, people who are testing xen on all of their
systems will most likely be doing so with a real clone of the repo,
and not one with a bunch of random patches, I would think.

IP> I guess it doesn't really hurt providing people know what they're
IP> doing.

I think the people who don't know what they're doing won't know that
it's not part of the larger changeset ID, which means they'll copy the
whole thing when posting a bug, which gets the info there anyway.

Would it be better to tuck the sequence number away somewhere else?  I
think that would be a bit overkill, but if anyone has strong feelings
about it, I can do it.  Perhaps adding "xen_build" to "xen_major" and
"xen_minor"?

-- 
Dan Smith
IBM Linux Technology Center
Open Hypervisor Team
email: danms@xxxxxxxxxx


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