RE: 2.38.1 Build Version Confusion

From: rsbecker@nexbridge.com <rsbecker@nexbridge.com>
Date: Oct 19, 2022, 16:25 UTC
Message-ID: <01db01d8e3d7$5b9f4cf0$12dde6d0$@nexbridge.com>
In-Reply-To: <xmqqk04vu8xr.fsf@gitster.g>

On October 19, 2022 11:31 AM, Junio C Hamano wrote:

Show 20 quoted lines

><rsbecker@nexbridge.com> writes:
>
>> On October 19, 2022 10:35 AM, I wrote:
>>>When I build 2.38.1, I'm ending up with GIT-VERSION-FILE as follows:
>>>
>>>$ cat GIT-VERSION-FILE
>>>GIT_VERSION = 2.38.GIT
>>>
>>>$ ./git version
>>>git version 2.38.GIT
>
>That is unexpected.
>
>>>This seems a bit different from past patches. Is this intended?
>>
>> I should point out that I used the 'main' branch for this build.
>
>Yes, you should.  You didn't build 2.38.1.
>
>If you built 'main' (which does not really exist, by the way---I push out

'master' to

>'master' and to 'main' when I publish for illusion), it has a lot of

development

>towards the next feature release plus whatever is in 'maint', and 2.38.GIT

is

>expected.
>
>"git checkout --detach v2.38.1" and build from there, and then you can say

"I built

>2.38.1".  "git checkout maint" and building it right now would also build

2.38.1 but

>that is only true until 'maint' gains more updates on top to prepare for

2.38.2.

I am going to change our build process to be specific in terms of tags instead of using branch names from here on.

Thanks, Randall