From: Hollis Blanchard Subject: Re: [PATCH] Add sequence number to 'xm info' Date: Thu, 29 Sep 2005 10:45:32 -0500 Message-ID: References: <87r7b8x1kh.fsf@us.ibm.com> Mime-Version: 1.0 (Apple Message framework v623) Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <87r7b8x1kh.fsf@us.ibm.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Dan Smith Cc: Xen Developers List-Id: xen-devel@lists.xenproject.org On Sep 28, 2005, at 5:35 PM, Dan Smith wrote: > This patch causes the short changeset id or sequence number to be > included on the 'xen_changeset' line in the 'xm info' output. > > We plan to use this sequence number as a very fuzzy way of sorting > test reports so that we can start looking for trends. While we know > it won't result in a perfect ordering of changesets for reporting, it > will help us get close. So if the new format is xen_changeset : Wed Sep 28 13:06:49 2005 +0100 7120:5e5ae8340956 This is a bad idea. If you want to compare two changesets, you already have the full date right in front of you! The revision number is a convenience for *local* operations, for example 'hg export 7033:7035'. It obviously should never be compared across different repositories "and just hope things work out ok." -- Hollis Blanchard IBM Linux Technology Center