From: Johannes Schindelin <johannes.schindelin@gmx.de>
To: git-for-windows@googlegroups.com, git@vger.kernel.org,
git-packagers@googlegroups.com
Cc: Johannes Schindelin <johannes.schindelin@gmx.de>
Subject: [ANNOUNCE] Git for Windows 2.39.0-rc1
Date: Wed, 30 Nov 2022 15:57:31 +0000 [thread overview]
Message-ID: <20221130155732.3246-1-johannes.schindelin@gmx.de> (raw)
Dear Git users,
I hereby announce that Git for Windows 2.39.0-rc1 is available from:
https://github.com/git-for-windows/git/releases/tag/v2.39.0-rc1.windows.1
Changes since Git for Windows v2.38.1 (October 18th 2022)
New Features
* Comes with Git v2.39.0-rc1.
* Comes with OpenSSL v1.1.1s.
* Comes with cURL v7.86.0.
* The Portable Git edition (which comes as a self-extracting 7-Zip
archive) now uses the latest 7-Zip version to self-extract.
* Comes with OpenSSH v9.1p1.
* It is now possible to generate and use SSH keys protected by
security keys (AKA FIDO devices) via Windows Hello, e.g. via
ssh-keygen.exe -t ecdsa-sk.
* Portable Git no longer configures color.diff, color.status and
color.branch individually, but configures color.ui instead, which
makes it easier to override the default.
* Comes with GNU TLS v3.7.8.
* Comes with Git Credential Manager Core v2.0.877.
* Comes with MinTTY v3.6.2.
* Comes with Bash v5.2 patchlevel 12.
Bug Fixes
* The Git executables (e.g. git.exe itself) used to have incomplete
version information recorded in their resources, which has been
fixed.
* A regression introduced in Git for Windows v2.38.0 that prevented
git.exe from running in Windows Nano Server containers was fixed.
Git-2.39.0-rc1-64-bit.exe | ea2412da9d24706a9f600d34136536e281b1ec5d67ab04cb2edfeb16eb39fc33
Git-2.39.0-rc1-32-bit.exe | aa4fc74ee343fb8e172a69ecb28b215cba84e93c70d1d25b15c70a24966bfb03
PortableGit-2.39.0-rc1-64-bit.7z.exe | dd568bd0fab26f8660a89b125b91c0f681b2b7c235681973bbd886498a62070c
PortableGit-2.39.0-rc1-32-bit.7z.exe | 0c29213329d702efaeda39bccadbda7edf7eded113a68e2b0b4c7242ac6432ae
MinGit-2.39.0-rc1-64-bit.zip | d0bf3d86da0571cfc99b39d9b06c1d58136870e0dde0235db6b3f22685633072
MinGit-2.39.0-rc1-32-bit.zip | 43f658e613de064c38619dcffa51d2fa4e55a4035f6b46054b8342613767a2de
MinGit-2.39.0-rc1-busybox-64-bit.zip | 5c4e74bc0f6d731e9fbc8693c4bfe25ea6b172d38adf70ff0c2d1015c7288f46
MinGit-2.39.0-rc1-busybox-32-bit.zip | eaaf0444b95ab48f442e7a7375dfac0e97c1547afb348a627c70795ec5edb5e2
Git-2.39.0-rc1-64-bit.tar.bz2 | 5db8ec7346080deceed5ee7f7e6c8025b4621954e0772873f1c8c528508979dc
Git-2.39.0-rc1-32-bit.tar.bz2 | db2b57ab50f4e4a5e225842f8ff31bc849ab0c5961fbdd177b3e92c45b6ba859
Ciao,
Johannes
reply other threads:[~2022-11-30 15:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221130155732.3246-1-johannes.schindelin@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).