[ANNOUNCE] Git for Windows 2.28.0-rc0

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Jul 10, 2020, 13:59 UTC
Message-ID: <20200710135935.6416-1-johannes.schindelin@gmx.de>

Dear Git users,

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

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

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

New Features

  * Comes with Git v2.28.0-rc0.
  * Comes with subversion v1.14.0.
  * Comes with MSYS2 runtime (Git for Windows flavor) based on Cygwin
    3.1.5.
  * 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.
  * 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-rc0-64-bit.exe | 11373dd9d740ede0e5f54776eddb1591578fc5917422d656187e9b37b3960b94 Git-2.28.0-rc0-32-bit.exe | b238446edfee249c59c57143cfd69baf83d8bdedda31c5e93fd4b9092bf41cbb PortableGit-2.28.0-rc0-64-bit.7z.exe | 8d09850454bf8812c944b746ebcdaa86489c3f843f19d64bf23caeaac7572b2a PortableGit-2.28.0-rc0-32-bit.7z.exe | ad4c123c88a0789c00a8a825022a6eb850ce1292b5f3d17b6f9445d81a819474 MinGit-2.28.0-rc0-64-bit.zip | cae926ba5e2d2ed5a09bb0ea78470f856800ed62b7c330e4bab89b0044724762 MinGit-2.28.0-rc0-32-bit.zip | 80c7b58d1ad819de3d9d4aa95624c4ec2880d3d19b74b41969b34e905d245b40 MinGit-2.28.0-rc0-busybox-64-bit.zip | 0a0ef355a90d31c57bfed86547306076e7a825eb21e325990687e1d030c50c8c MinGit-2.28.0-rc0-busybox-32-bit.zip | 097a3cc7d70345fea42ab4801d438b882a5e1cf5d8431e00f52af7569acd6e27 Git-2.28.0-rc0-64-bit.tar.bz2 | 220bf0b98bedaf9ef5710a40c5d7ab13c0c979760971332221d38255f3ad8e92 Git-2.28.0-rc0-32-bit.tar.bz2 | e97222bae9c5a4736b9a28a8812917a9a20c160786c0ec624dde3037db0568c5

Ciao, Johannes