From owner-freebsd-current@freebsd.org Sun Jan 3 11:07:55 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 072F34CDD31 for ; Sun, 3 Jan 2021 11:07:55 +0000 (UTC) (envelope-from uqs@freebsd.org) Received: from acme.spoerlein.net (acme.spoerlein.net [IPv6:2a05:fc87:1:5::15]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "www.spoerlein.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4D7wwB47wcz4m44 for ; Sun, 3 Jan 2021 11:07:54 +0000 (UTC) (envelope-from uqs@freebsd.org) Received: from localhost (acme.spoerlein.net [IPv6:2a05:fc87:1:5:0:0:0:15]) by acme.spoerlein.net (8.16.1/8.15.2) with ESMTPS id 103B7iE0078636 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Sun, 3 Jan 2021 12:07:44 +0100 (CET) (envelope-from uqs@freebsd.org) Date: Sun, 3 Jan 2021 12:07:44 +0100 From: Ulrich =?utf-8?B?U3DDtnJsZWlu?= To: Graham Perrin Cc: FreeBSD Current , Michael Gmelin Subject: Re: Finding a commit in cgit, given output from uname -a Message-ID: Mail-Followup-To: Graham Perrin , FreeBSD Current , Michael Gmelin References: <8C3C23B7-18EC-43FA-A0C3-370E79829A9A@grem.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/2.0.1 (2020-11-14) X-Rspamd-Queue-Id: 4D7wwB47wcz4m44 X-Spamd-Bar: / X-Spamd-Result: default: False [0.00 / 15.00]; local_wl_from(0.00)[freebsd.org]; ASN(0.00)[asn:39540, ipnet:2a05:fc87::/32, country:CH] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jan 2021 11:07:55 -0000 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 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@mowa219-gjp4-8570p:/usr/obj/usr/src/freebsd-current/amd64.amd64/sys/GENERIC-NODEBUG amd64 >>> >>> finds nothing. >>> >>> Am I missing something? >> Remove “g” from the hash. >> >> -m > > >Thank you! > >I had bookmarked > >without noticing the accuracy of Ed Maste's ASCII (pointing at the first >character _after_ the g) and >, >which wondered about a typo. > >Now I see: > > > >Probably an obvious question, does the 'g' signify Git? Yes, from git-describe(1): With something like git.git current tree, I get: [torvalds@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