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] hg changeset numbers vs hashes and the "public" xen http

To: Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>
Subject: Re: [Xen-devel] hg changeset numbers vs hashes and the "public" xen http-hg trees
From: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
Date: Fri, 13 Aug 2010 15:56:57 +0100
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 13 Aug 2010 07:58:31 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <92bc5518-dfad-4e97-831b-d4811db07f0b@default>
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>
Organization: Citrix Systems, Inc.
References: <92bc5518-dfad-4e97-831b-d4811db07f0b@default>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Fri, 2010-08-13 at 15:44 +0100, Dan Magenheimer wrote:
> I've started to notice developers making more use
> of the 48-bit "hash" (forgot the proper term) identifier
> for changesets instead of changeset number.  While
> I understand the reasons (specifically that the
> 48-bit has is unique across all trees but the changeset
> number is not... and that more developers are experienced
> now with git where the hash is exclusively used), sadly
> the "public" http representation of Xen trees available
> through:
> http://xenbits.xensource.com/xen-unstable.hg and friends
> which I browse regularly does not allow searching by hash,
> so a cset comment such as:
> "tools/python: Remove non-ASCII characters introduced by fffedd3d70e1."
> is rather useless when using the http interface.

Typing "fffedd3d70e1" in the search box at
http://xenbits.xensource.com/xen-unstable.hg takes me to 
http://xenbits.xensource.com/xen-unstable.hg?rev=fffedd3d70e1 which has
21967:fffedd3d70e1 as the first listed entry and as far as I know this
has always worked for me (I use it all the time).

It might be one click extra than you were expecting but it is certainly

Even if not then clicking on the first entry on
http://xenbits.xensource.com/xen-unstable.hg then editing the URL to
change the hash is not that hard. In fact if you use it regularly then
an alias can usually be setup in most browsers to take you straight to
the relevant page if you type e.g. "xen fffedd3d70e1" in the address

Note that the cset number is not stable even within
http://xenbits.xensource.com/xen-unstable.hg -- if a merge changeset is
pushed to this tree I believe it is possible that changesets already
their could change their numbers.


Xen-devel mailing list

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