[ANNOUNCE] Git for Windows 2.28.0-rc1
To
git-for-windows@googlegroups.com
git@vger.kernel.org
git-packagers@googlegroups.com
Cc
Johannes Schindelin
From
Johannes Schindelin
Date
2020-07-18 01:10:07 UTC
Dear Git users,

I hereby announce that Git for Windows 2.28.0-rc1 is available from:

    https://github.com/git-for-windows/git/releases/tag/v2.28.0-rc1.windows.1

Changes since Git for Windows v2.27.0 (June 1st 2020)

New Features

  * Comes with Git v2.28.0-rc1.
  * Comes with subversion v1.14.0.
  * Comes with the designated successor of Git Credential Manager for
    Windows (GCM for Windows), the cross-platform Git Credential
    Manager Core. For now, this is opt-in, with the idea of eventually
    retiring GCM for Windows.
  * Comes with cURL v7.71.1.
  * Comes with Perl v5.32.0.
  * Comes with MSYS2 runtime (Git for Windows flavor) based on Cygwin
    3.1.6 (including the improvements of Cygwin 3.1.5).
  * Comes with GNU Privacy Guard v2.2.21.

Bug Fixes

  * A typo was fixed in the installer.
  * The new git pull behavior option now records the fast-forward
    choice correctly.
  * In v2.27.0, git svn was broken completely, which has been fixed.
  * Some Git operations could end up with bogus modified symbolic links
    (where git status would report changes but git diff would not),
    which is now fixed.
  * When reinstalling (or upgrading) Git for Windows, the "Pseudo
    Console Support" choice is now remembered correctly.
  * Under certain circumstances, the Git Bash window (MinTTY) would
    crash frequently, which has been addressed.
  * When pseudo console support is enabled, the VIM editor sometimes
    had troubles accepting certain keystrokes, which was fixed.
  * Due to a bug, it was not possible to disable Pseudo Console support
    by reinstalling with the checkbox turned off, which has been fixed.
  * A bug with enabled Pseudo Console support, where git add -i would
    not quit the file selection mode upon an empty input, has been
    fixed.
  * The cleanup mode called "scissors" in git commit now handles CR/LF
    line endings correctly.
  * When cloning into an existing directory, under certain
    circumstances, the core.worktree option was set unnecessarily. This
    has been fixed.

Git-2.28.0-rc1-64-bit.exe | 15a73c06141512c93dd0ad92f0aba1628bd6294162b44fb24baba7d05e5c636c
Git-2.28.0-rc1-32-bit.exe | 1a12463d484068e73b218a9a1d2d98b7924699fefbc7baa4a06054ea8a6597cb
PortableGit-2.28.0-rc1-64-bit.7z.exe | 90f6bc4ba6af69375acb286c45fa2ec01d91b0e67a4d851a9e9d7507e8486437
PortableGit-2.28.0-rc1-32-bit.7z.exe | c4e0e659e34f47e679c9882b2bc3c184e0b6ca58f850ce91764cfc19d5f002f3
MinGit-2.28.0-rc1-64-bit.zip | 08edf0ea9f94e511eea3abcc1c3fab6967bbf6e14fe7dcf619c3218b6f038c66
MinGit-2.28.0-rc1-32-bit.zip | ee21cc0648bf2e0f96e331fd6f8a4af4cd01375e18c8980a835baa148b0c1b81
MinGit-2.28.0-rc1-busybox-64-bit.zip | 76b1e67705bd7ea92364e286a6d3e35a1c5b5fb47b80f4cc82a581e478464e99
MinGit-2.28.0-rc1-busybox-32-bit.zip | 2a53b2e632e039a4ed0db3656c6d8394df4111bfcd5ca263067c62ddfff2a3f7
Git-2.28.0-rc1-64-bit.tar.bz2 | 62b70980b712be2ff02b264b77f645d260651053d58eec0191838eaf6b1d59d5
Git-2.28.0-rc1-32-bit.tar.bz2 | cccf7f9696945b2b471fcc4dcad296d61382205bb8d8d64b0a84e950bf1d20d9

Ciao,
Johannes