Speeding up slower Git operations

[Shawn Webb]

On Mon, Jun 24, 2019 at 12:46:41PM -0400, Ed Maste wrote:
> On Tue, 28 May 2019 at 08:18, Ed Maste <emaste at freebsd.org> wrote:
> >
> > Today for builds from git we include in uname the corresponding SVN
> > version, the git hash, and the branch - e.g. a test machine here
> > reports "r333291+95e9f145d658(HEAD-TESTING)". I'm not sure what the
> > best way to report it would be, but in the absence of svn we could
> > indicate something like
> > "95e9f145d658(HEAD-TESTING) c251421".
> 
> This idea is implemented in review D20462,
> https://reviews.freebsd.org/D20462
> 
> Here's an example from a test machine of mine:
> # uname -a
> FreeBSD test 13.0-CURRENT FreeBSD 13.0-CURRENT
> 322839cffdb-c260903(wipbsd.20190326) GENERIC  amd64

Is there any real use for the monotonically increasing version number
in git? For example, can I go from c27 to git commit hash?

Pardon my naive tone. This is a part of git I don't know well.

Thanks,

-- 
Shawn Webb
Cofounder / Security Engineer
HardenedBSD

Tor-ified Signal:    +1 443-546-8752
Tor+XMPP+OTR:        lattera at is.a.hacker.sx
GPG Key ID:          0xFF2E67A277F8E1FA
GPG Key Fingerprint: D206 BB45 15E0 9C49 0CF9  3633 C85B 0AF8 AB23 0FB2
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-git/attachments/20190624/d08c7ba3/attachment.sig>