Re: Finding a commit in cgit, given output from uname -a

On Sat, 2021-01-02 at 19:21:44 +0000, Graham Perrin wrote:
>On 02/01/2021 18:53, Michael Gmelin wrote:
>
>>> On 2. Jan 2021, at 19:44, Graham Perrin <grahamperrin_at_gmail.com> wrote:
>>>
>>> FreeBSD mowa219-gjp4-8570p 13.0-CURRENT FreeBSD 13.0-CURRENT #0 main-c530-g8b4c3a03f: Fri Jan  1 15:27:15 GMT 2021 root_at_mowa219-gjp4-8570p:/usr/obj/usr/src/freebsd-current/amd64.amd64/sys/GENERIC-NODEBUG amd64
>>>
>>> <https://cgit.freebsd.org/src/log/?qt=range&q=g8b4c3a03f> finds nothing.
>>>
>>> Am I missing something?
>> Remove “g” from the hash.
>>
>> -m
>
>
>Thank you!
>
>I had bookmarked
><https://lists.freebsd.org/pipermail/freebsd-current/2020-December/077990.html>
>without noticing the accuracy of Ed Maste's ASCII (pointing at the first
>character _after_ the g) and
><https://lists.freebsd.org/pipermail/freebsd-current/2020-December/078005.html>,
>which wondered about a typo.
>
>Now I see:
>
><https://lists.freebsd.org/pipermail/freebsd-current/2020-December/078009.html>
>
>Probably an obvious question, does the 'g' signify Git?

Yes, from git-describe(1):

        With something like git.git current tree, I get:

            [torvalds_at_g5 git]$ git describe parent
            v1.0.4-14-g2414721

        i.e. the current head of my "parent" branch is based on v1.0.4, but
        since it has a few commits on top of that, describe has added the
        number of additional commits ("14") and an abbreviated object name for
        the commit itself ("2414721") at the end.

        The number of additional commits is the number of commits which would
        be displayed by "git log v1.0.4..parent". The hash suffix is "-g" +
        unambiguous abbreviation for the tip commit of parent (which was
        2414721b194453f058079d897d13c4e377f92dc6). The "g" prefix stands for
        "git" and is used to allow describing the version of a software
        depending on the SCM the software is managed with. This is useful in an
        environment where people may use different SCMs.

Mercurial of course cannot use 'h', as that is a valid char in hex and 
could be confused with the hash itself :(

hth
Uli