hg changeset numbers vs hashes and the "public" xen http-hg trees

[Dan Magenheimer <dan.magenheimer@oracle.com>]

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.

Is it possible that an update to the xensource hg-http server
might solve this problem?

Alternately, maybe it might be time to switch from mercurial
to git?  :-) (start another thread to comment on that please)

Thanks,
Dan