From: Junio C Hamano <gitster@pobox.com>
To: <rsbecker@nexbridge.com>
Cc: <git@vger.kernel.org>
Subject: Re: 2.38.1 Build Version Confusion
Date: Wed, 19 Oct 2022 08:31:12 -0700 [thread overview]
Message-ID: <xmqqk04vu8xr.fsf@gitster.g> (raw)
In-Reply-To: <01d101d8e3cb$ab9d7940$02d86bc0$@nexbridge.com> (rsbecker@nexbridge.com's message of "Wed, 19 Oct 2022 11:01:24 -0400")
<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.
HTH.
next prev parent reply other threads:[~2022-10-19 15:51 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 [this message]
2022-10-19 16:25 ` rsbecker
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=xmqqk04vu8xr.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=rsbecker@nexbridge.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).