From: <rsbecker@nexbridge.com>
To: "'Junio C Hamano'" <gitster@pobox.com>
Cc: <git@vger.kernel.org>
Subject: RE: 2.38.1 Build Version Confusion
Date: Wed, 19 Oct 2022 12:25:04 -0400 [thread overview]
Message-ID: <01db01d8e3d7$5b9f4cf0$12dde6d0$@nexbridge.com> (raw)
In-Reply-To: <xmqqk04vu8xr.fsf@gitster.g>
On October 19, 2022 11:31 AM, Junio C Hamano wrote:
><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
next prev parent reply other threads:[~2022-10-19 16:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-19 14:34 2.38.1 Build Version Confusion rsbecker
2022-10-19 15:01 ` rsbecker
2022-10-19 15:31 ` Junio C Hamano
2022-10-19 16:25 ` rsbecker [this message]
2022-10-19 15:06 ` Taylor Blau
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='01db01d8e3d7$5b9f4cf0$12dde6d0$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).