| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
Re: [Xen-devel] hg changeset numbers vs hashes and the "public" xen http
At 15:44 +0100 on 13 Aug (1281714259), 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.
Works for me[tm]. I just entered fffedd3d70e1 in the search box and it
took me to that place in the log.
Cheers,
Tim.
--
Tim Deegan <Tim.Deegan@xxxxxxxxxx>
Principal Software Engineer, XenServer Engineering
Citrix Systems UK Ltd. (Company #02937203, SL9 0BG)
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home