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-rc0
Date: Wed, 23 Nov 2022 12:27:53 +0000 [thread overview]
Message-ID: <20221123122753.3132-1-johannes.schindelin@gmx.de> (raw)
Dear Git users,
I hereby announce that Git for Windows 2.39.0-rc0 is available from:
https://github.com/git-for-windows/git/releases/tag/v2.39.0-rc0.windows.1
Changes since Git for Windows v2.38.1 (October 18th 2022)
* Comes with OpenSSL v1.1.1q.
New Features
* Comes with Git v2.39.0-rc0.
* 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.
* Comes with Bash v5.2 patchlevel 009 .
* 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.
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-rc0-64-bit.exe | 74ba237e120c4528102001551f2b2c08a9643a6cad8d7a397b134e4dde5498ef
Git-2.39.0-rc0-32-bit.exe | 0c14e81e0746a151ca8937c3736160720b4cfecf9bc826f681de7f275978ab51
PortableGit-2.39.0-rc0-64-bit.7z.exe | 02e73e5f584df658a709f373b0e0b8dc7ff72a754052bd76cd0af67fa23a9701
PortableGit-2.39.0-rc0-32-bit.7z.exe | 2c6acc55ea0df14be2b1695445ec6ac9061eb6e5a0f50ee8d9a1054899e522c2
MinGit-2.39.0-rc0-64-bit.zip | 638acc223365fc761655926b2cd86d9f4e2b6618a7ddee183a31c26dd3a63714
MinGit-2.39.0-rc0-32-bit.zip | bc3c16ba093821ffb254a6c2eb44a9f84de163543f657e03ca1b797a826ab80c
MinGit-2.39.0-rc0-busybox-64-bit.zip | f898d769d717c85f380f65687b10734aa5cfb28b636805b7bf434b5c24dbc593
MinGit-2.39.0-rc0-busybox-32-bit.zip | bd79b74dac8b69a8eba4c5324b5190dd85c71b74ffb8e2ca20358d94e244ec00
Git-2.39.0-rc0-64-bit.tar.bz2 | 48f2855ec77fb608f3831b1aaab725ca599e42a8fb27c6aa6c872c4d3f2f9efd
Git-2.39.0-rc0-32-bit.tar.bz2 | 036afe5dda8cb98e70bbcbce92570dfe0bc6d6f82f2fb7e0129faf17b62eeb4f
Ciao,
Johannes
next reply other threads:[~2022-11-23 12:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-23 12:27 Johannes Schindelin [this message]
2022-11-24 23:44 ` [ANNOUNCE] Git for Windows 2.39.0-rc0 Junio C Hamano
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=20221123122753.3132-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).