From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: git-for-windows@googlegroups.com, git@vger.kernel.org,
git-packagers@googlegroups.com
Subject: Re: [ANNOUNCE] Git for Windows 2.41.0-rc0
Date: Wed, 17 May 2023 16:13:07 +0200 (CEST) [thread overview]
Message-ID: <9a1c44a7-e1c9-1ab7-0950-c128fb75490c@gmx.de> (raw)
In-Reply-To: <20230517135216.3546-1-johannes.schindelin@gmx.de>
Addendum:
Please also note that the code-signing certificate used to sign Git for
Windows' executables was renewed and may cause Smart Screen to show a
warning until the certificate has gained a certain minimum reputation.
This is nothing to worry about, it is just the regular code-signing
certificate renewal mechanics. If you want to make extra certain that you
got the correct file, please just compare the SHA-256 checksum against the
one listed below.
Oh, and please test! This is _the_ chance we have to hammer out a solid,
robust Git for Windows v2.41.0.
Thank you,
Johannes
On Wed, 17 May 2023, Johannes Schindelin wrote:
> Dear Git users,
>
> I hereby announce that Git for Windows 2.41.0-rc0 is available from:
>
> https://github.com/git-for-windows/git/releases/tag/v2.41.0-rc0.windows.1
>
> Changes since Git for Windows v2.40.1 (April 25th 2023)
>
> As announced previously, Git for Windows will drop support for Windows
> 7 and for Windows 8 in one of the next versions, following Cygwin's and
> MSYS2's lead (Git for Windows relies on MSYS2 for components such as
> Bash and Perl).
>
> Following the footsteps of the MSYS2 and Cygwin projects on which Git
> for Windows depends, the 32-bit variant of Git for Windows is being
> phased out. As of Git for Windows v2.41.0, the 32-bit variant of the
> POSIX emulation layer (known as "MSYS2 runtime", powering Git Bash
> among other components shipped with Git for Windows) is in maintenance
> mode and will only see security bug fixes (if any). Users relying on
> 32-bit Git for Windows are highly encouraged to switch to the 64-bit
> version whenever possible.
>
> New Features
>
> * Comes with Git v2.41.0-rc0.
> * Comes with OpenSSH v9.3p1
> * Comes with cURL v8.0.1.
> * Comes with MinTTY v3.6.4.
> * The Git for Windows installer now also includes the Git LFS
> documentation (i.e. git help git-lfs now works).
> * Comes with Perl v5.36.1.
> * Comes with GNU Privacy Guard v2.2.41.
> * Comes with Git Credential Manager v2.1.2.
> * Comes with MSYS2 runtime (Git for Windows flavor) based on Cygwin
> 3.4.6. (This does not extend to 32-bit Git for Windows, which is
> stuck with v3.3.* of the MSYS2 runtime forever.)
> * To help with Git for Windows' release mechanics, Git for Windows
> now ships with two variants of libcurl.
>
> Bug Fixes
>
> * Git GUI's Repository>Explore Working Copy was broken since v2.39.1,
> which has been fixed.
>
> Git-2.41.0-rc0-64-bit.exe | 7b0bfa1e1e059f7bc5e5a5a172f3da0fac8e1f5b6011366527ed6afcc50a82aa
> Git-2.41.0-rc0-32-bit.exe | 2048117413bdda01eaa358f9451973876e0e06b7011fe0636f8df794b6b5ad8f
> PortableGit-2.41.0-rc0-64-bit.7z.exe | 09085f5414f97e406b13a023482684d2728bb9788eca687dbf19434ab157ef96
> PortableGit-2.41.0-rc0-32-bit.7z.exe | cff7a350d6b312112b1cf4eb33344f37a6c85bdca8dc07ce90a23752b01abd47
> MinGit-2.41.0-rc0-64-bit.zip | 7b45fc53600f19008d322848305551fbc5600136caae0769ee6d10774c3688a4
> MinGit-2.41.0-rc0-32-bit.zip | c49966732c4ba4b8c76057c2ebc13981f39be728c454aaf5849db3833ce049a9
> MinGit-2.41.0-rc0-busybox-64-bit.zip | 8792014287b6327bccec16f1ad7d970b10f0566b667f40c57462e6e27b98e0fd
> MinGit-2.41.0-rc0-busybox-32-bit.zip | 67030d81d36caf0febab51d0fd1e3f20d2441197b3ca306d41f5f7658c3399a1
> Git-2.41.0-rc0-64-bit.tar.bz2 | e741dc0cc7211e974d588f624fa566a4b92e50317e3f735894b443583c8e5d0e
> Git-2.41.0-rc0-32-bit.tar.bz2 | 0c0a97258b36b1054c97379b59ad5fe674e539d366618e7df1bc2e20e5666c5d
>
> Ciao,
> Johannes
>
prev parent reply other threads:[~2023-05-17 14:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 13:52 [ANNOUNCE] Git for Windows 2.41.0-rc0 Johannes Schindelin
2023-05-17 14:13 ` Johannes Schindelin [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=9a1c44a7-e1c9-1ab7-0950-c128fb75490c@gmx.de \
--to=johannes.schindelin@gmx.de \
--cc=git-for-windows@googlegroups.com \
--cc=git-packagers@googlegroups.com \
--cc=git@vger.kernel.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).