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] c/s 20384

To: Jan Beulich <JBeulich@xxxxxxxxxx>
Subject: Re: [Xen-devel] c/s 20384
From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Date: Tue, 03 Nov 2009 11:06:03 -0800
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Delivery-date: Tue, 03 Nov 2009 11:12:29 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4AF00F6B020000780001D4BA@xxxxxxxxxxxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <4AEEA3BB020000780001D146@xxxxxxxxxxxxxxxxxx> <4AEF4A54.2030806@xxxxxxxx> <4AF00F6B020000780001D4BA@xxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20091014 Fedora/3.0-2.8.b4.fc11 Lightning/1.0pre Thunderbird/3.0b4
On 11/03/09 02:09, Jan Beulich wrote:
> Hmm, I think http://xenbits.xensource.com/xen-unstable.hg can
> reasonably be considered a canonical reference, and hence I would
> assume that using the small number ids is uniquely identifying a c/s.

I have a repo here which is what I'm going to refer to if you highlight
a particular changeset for some reason.  If I have to go back to xenbits
to map a local change number to a changeset id then that's pretty
awkward (particularly if I'm not online at the time).

> Furthermore, using the full ids doesn't allow easily judging how long
> ago the referred to c/s was committed, including immediately knowing
> which releases it may have been part of.

That's pretty easy to determine once you look it up.  I don't know that
I have a good idea about how change numbers relate to releases anyway.


Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>