From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <johannes.schindelin@gmx.de>
Cc: git-for-windows@googlegroups.com, git@vger.kernel.org,
git-packagers@googlegroups.com
Subject: Re: [ANNOUNCE] Git for Windows 2.39.0-rc0
Date: Fri, 25 Nov 2022 08:44:02 +0900 [thread overview]
Message-ID: <xmqqpmdbkjel.fsf@gitster.g> (raw)
In-Reply-To: <20221123122753.3132-1-johannes.schindelin@gmx.de> (Johannes Schindelin's message of "Wed, 23 Nov 2022 12:27:53 +0000")
Johannes Schindelin <johannes.schindelin@gmx.de> writes:
> 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.
Thanks!
prev parent reply other threads:[~2022-11-24 23:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-23 12:27 [ANNOUNCE] Git for Windows 2.39.0-rc0 Johannes Schindelin
2022-11-24 23:44 ` 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=xmqqpmdbkjel.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git-for-windows@googlegroups.com \
--cc=git-packagers@googlegroups.com \
--cc=git@vger.kernel.org \
--cc=johannes.schindelin@gmx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.