From: Junio C Hamano <gitster@pobox.com>
To: Michael Cheel <mcheel@axxess.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Git Version Confusion
Date: Wed, 22 Jan 2025 09:43:29 -0800 [thread overview]
Message-ID: <xmqq5xm6ycam.fsf@gitster.g> (raw)
In-Reply-To: <SJ0PR10MB4750C74BF6A4A26AF4730BCFBBE12@SJ0PR10MB4750.namprd10.prod.outlook.com> (Michael Cheel's message of "Wed, 22 Jan 2025 16:57:25 +0000")
Michael Cheel <mcheel@axxess.com> writes:
> Can anyone tell me why the git home page says the latest version
> is 2.48.1 (released 2025-01-13) but then the download page (for
> windows) says 2.47.1(2) released 2025-01-14? It is a bit confusing
> to me.
The 2.48.1 is the official source release and the latest. Depending
on the platform and distribution, some may lag behind releasing the
latest and that is perfectly expected.
Looking at the output from
https://lore.kernel.org/git/?q=s:Announce+f:Schindelin
I suspect that Windows binary based on 2.48.1 has not been released
yet, even though one based on 2.47.1 has.
prev parent reply other threads:[~2025-01-22 17:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-22 16:57 Git Version Confusion Michael Cheel
2025-01-22 17:43 ` Junio C Hamano [this message]
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=xmqq5xm6ycam.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=mcheel@axxess.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).