Re: [ANNOUNCE] Git v2.48.1 and friends
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Jan 15, 2025, 05:27 UTC
- Message-ID
- <xmqqikqg1wav.fsf@gitster.g>
- In-Reply-To
- <047401db66f1$f4ba6790$de2f36b0$@nexbridge.com>
<rsbecker@nexbridge.com> writes:
Show 14 quoted lines
> On January 14, 2025 8:28 PM, Junio C Hamano wrote: > ... >>Will it be the resulting checkout of "git clone --single" of that tag? > Then you can go >>there and say "make", and as Dscho explained, what Dscho wrote in DEF_VER > does >>not matter. The tag that points at that checked out commit is v2.47.2 and > that is >>what resulting "git version" would say. >> ... > In order to accept our builds, the NonStop community needs to be able to > correlate what we build to a real commit from the git git repository. We > cannot > build from tarballs, as this cannot be certified by the community users.
So you are going to build by having a clone of my repository that is updated via "git fetch" to have these latest tags, and you will check out the v2.47.2 tag or the "maint-2.47" branch whose tip happens to be at that tag. And say "make" in there. We may have a wrong string in DEF_VAR in its GIT-VERSION-GEN file, but as you read already in the above, it does not matter. Saying "make" would run GIT-VERSION-GEN script, which notices that you are in a Git repository and not in a tarball extract, and runs "git describe" on the commit you are building from, instead of blindly relying on the value in DEF_VAR.
Which means your build will result in a version of git that says "2.47.2" when "git version" is run.
So is there still a problem? I am puzzled.