From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: c/s 20384 Date: Tue, 03 Nov 2009 11:06:03 -0800 Message-ID: <4AF07F1B.4090803@goop.org> References: <4AEEA3BB020000780001D146@vpn.id2.novell.com> <4AEF4A54.2030806@goop.org> <4AF00F6B020000780001D4BA@vpn.id2.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4AF00F6B020000780001D4BA@vpn.id2.novell.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: Jan Beulich Cc: xen-devel@lists.xensource.com, Keir Fraser List-Id: xen-devel@lists.xenproject.org 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. J