Re: git: a1097094c4c5 - main - newvers: Set explicit git revision length

Addressing John's other point:

> > I guess is that how many other user git settings can affect the build?  Should
> > we not require an empty global git config as a prereq for someone who wants a
> > reproducible build (and use the same setup for our official builds) and say
> > that if you adjust your user config to impact the build that's kind of your
> > problem?

I think if the user adjusts their git config in a way that changes
file content (e.g. scripted $FreeBSD$ expansion as was discussed early
on in the git migration) that's their problem. Config that affects the
output format of the command does need to be addressed. This is really
no different to our build's use of things like `env -i LC_COLLATE=C
sort` which we already do. Usage in newvers is the only Git usage I'm
aware of that we need to address.