Re: Mercurial "r####" numbers are not stable, use commit ids

Stephen> I like Mercurial a little less every day. There is always a dark side I guess in every tool ... Stephen> *Always* post the log messages or commit ID, *never* the r Stephen> numbers. The r numbers are *not stable* across repositories, Stephen> and just confuse the readers. Even if the repository is updated by always pulling from http://hg.debian.org/hg/xemacs/xemacs? Stephen> You can get the commit IDs with "hg log" or "hg id". OK. I'll correct myself. Stephen> Somebody wrote to me: (In case the rest of you haven't figured it out by now, yes, it was I ...) What I see is this. A build from changeset: 4532:16906fefc8df branch: bytecomp-coding-system-2008-10-29 tag: tip user: Aidan Kehoe <kehoea(a)parhasard.net&gt; date: Sun Dec 21 17:23:06 2008 +0000 summary: Return a list copy in #'built-in-face-specifiers, pre-empting modification. works fine. A build from changeset: 4533:4a7c4ccac2fe tag: tip parent: 4527:8418d1ad4944 parent: 4532:16906fefc8df user: Aidan Kehoe <kehoea(a)parhasard.net&gt; date: Mon Dec 22 12:05:47 2008 +0000 summary: Merge. does not. However. I don't get this fully yet but it is getting clearer. Can it be so that Aidan merged in your changes on branch bytecomp-coding-system-2008-10-29 in the changeset 4533:4a7c4ccac2fe? So they surfaced first there for me. Yours -- %% Mats _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta