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
Date: Mon, 12 Dec 2022 17:00:42 +0000 [thread overview]
Message-ID: <20221212170042.3340-1-johannes.schindelin@gmx.de> (raw)
Dear Git users,
I hereby announce that Git for Windows 2.39.0 is available from:
https://gitforwindows.org/
Changes since Git for Windows v2.38.1 (October 18th 2022)
New Features
* Comes with Git v2.39.0.
* 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.
* Comes with Git LFS v3.3.0.
* Comes with PCRE2 v10.41.
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-64-bit.exe | 2eaba567e17784654be77ba997329742d87845c6f15e33c9620f9a331c69a976
Git-2.39.0-32-bit.exe | 5b01ddb342a07e74e723fe93bc84c275a19236e853c406b4496478e64a7f8add
PortableGit-2.39.0-64-bit.7z.exe | 8ca31e8474048b48b813ebdf95f288d58f253717d071d11785cc23f37dc6a396
PortableGit-2.39.0-32-bit.7z.exe | b8332fc12bcb1343d57c785d7ec140e2fd89f9d7f70309a00e79f9822c2cc855
MinGit-2.39.0-64-bit.zip | ae6863d7b7641ecf73f61edadbc7d1ff8259d08eccb4b9f006bb443d90910c25
MinGit-2.39.0-32-bit.zip | ad20467cf6a4c215b2c71f9bee192fb8ea1696fa3dda8e35e89544cdabdc1c7a
MinGit-2.39.0-busybox-64-bit.zip | a5d177bceeddfecc97c2340f0c8bc97d55ba113c4cd5b6b7d58e513dccb3d74f
MinGit-2.39.0-busybox-32-bit.zip | cb8371cbba56562f7af1d54281afb24bfa23395a57a0868398f644a79c2fea2a
Git-2.39.0-64-bit.tar.bz2 | ed78c21d89281d91fb1282043c3b618350e8ff721947ad01678356126b0447f3
Git-2.39.0-32-bit.tar.bz2 | 09126077d63b3e3e19c90599f86c037eb57edddf255e75acc31720428d03d78b
Ciao,
Johannes
reply other threads:[~2022-12-12 17:00 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221212170042.3340-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.
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).