[ANNOUNCE] Git for Windows 2.37.2

Dear Git users,

I hereby announce that Git for Windows 2.37.2 is available from:

    https://gitforwindows.org/

Changes since Git for Windows v2.37.1 (July 12th 2022)

(Upcoming) breaking changes

We updated the included Bash to version 5.1 (previously 4.4). Please check your shell scripts for potential compatibility issues.

Also, as previously announced, Git for Windows dropped support for Windows Vista.

Around the beginning of 2023, Git for Windows will drop support for Windows 7 and for Windows 8, following Cygwin's and MSYS2's lead (Git for Windows relies on MSYS2 for components such as Bash and Perl).

New Features

  * Comes with Git v2.37.2.
  * Comes with tig v2.5.6.
  * Comes with Bash v5.1 patchlevel 016 .
  * Comes with Perl v5.36.0.
  * Git's executables are now marked Terminal Server-aware, meaning:
    Git will be slightly faster when being run using Remote Desktop
    Services.
  * git svn is now based on subversion v1.14.2.
  * Comes with GNU TLS v3.7.7.

Bug Fixes

  * Git for Windows now ships without the zmore and bzmore utilities
    (which were broken and included only inadvertently).
  * A regression in the vimdiff mode of git mergetool has been fixed.
  * With certain network drives, it was reported that some attributes
    associated with caching confused Git for Windows. This was fixed.

Git-2.37.2-64-bit.exe | 9020623e95e8f250a6298aa98d4bce395adc121998a65bef143556c3fbd2462c Git-2.37.2-32-bit.exe | 3f1110d855a934194b8de1e032d8edcb622804a0b4223cccb9379f7d37a52915 PortableGit-2.37.2-64-bit.7z.exe | 71294d3008d6da6bd25527498ff726d09d55c2cbd1af32d8e99200d5339d7817 PortableGit-2.37.2-32-bit.7z.exe | 005253af6f96fc86a2ccec97dfd68c56f5b91f72c5cd953e5d1d240c35235390 MinGit-2.37.2-64-bit.zip | 197422464897cfc8f6ebd73007c798658d21310a4c32d43888c9e8f92720ffec MinGit-2.37.2-32-bit.zip | 77b39507cc4b06cad754137e08465c14532b3fc4b0bc4cfc3c91dfeaa6badbe8 MinGit-2.37.2-busybox-64-bit.zip | bfe43199e74d3d80ed7490b7f0aa09a92f907ecbe9ad80719a9bdf6a8ec4ae70 MinGit-2.37.2-busybox-32-bit.zip | a752814318a5cc0c00902d5fafffb97c7201ac2e837e0718eaeaddd3fdf3bb07 Git-2.37.2-64-bit.tar.bz2 | 0508cba06cc52b0e4e733cdd6ee19ad17cc67d31b69c34212f120c94f1806a98 Git-2.37.2-32-bit.tar.bz2 | f2612e4ff5d63d922673b1c6437b8c292ecdcfd950a2f0bdf4704d6eedc42def

Ciao, Johannes

Johannes Schindelin <johannes.schindelin@gmx.de> writes:

Thanks.

Johannes Schindelin wrote:

Just a heads-up: there was an issue with the process used to generate this version. Consequently, a large chunk of Git for Windows-specific changes (bugfixes, interoperability changes, etc.) is missing from this release.

A fixed release in in progress (see [1] for the latest updates, if you're interested). In the meantime, please *do not* use this version.

Thanks,
- Victoria

[1] https://github.com/git-for-windows/git/pull/3981

Victoria Dye <vdye@github.com> writes:

Sorry to see that it caused two cycles of release process. Would it have helped you if I had done things differently (other than "not issuing maintenance releases that are not security relevant"), perhaps giving a notice in advance by say a few days?

Thanks.

Hi Junio,

On Fri, 12 Aug 2022, Junio C Hamano wrote:

Thank you for offering to accommodate Git for Windows' needs.

In this instance, we tracked the problem down to https://github.com/gitgitgadget/git/issues/1321: When a rebase has a `pick` & `fixup` sequence and the `pick` failed and was skipped, then the `fixup` is still trying to amend `HEAD`, which is incorrect.

In this instance, that wreaked quite the havoc, dropping most of the Windows-specific changes due to mistaking the initial fake merge [*1*] for a real merge.

I offer a more verbose version of this analysis in https://github.com/git-for-windows/git/pull/3981#issuecomment-1212856115

Ciao, Dscho

Footnote *1*: In Git for Windows, we use the "merging-rebase" strategy where each rebase starts with a fake merge of the previous commit history ("fake" because it uses `-s ours` to avoid taking any actual content changes). The idea is that the patches will be as clean and ready to submit to upstream as possible by rebasing them, yet still be able to fast-forward. For more details, see https://github.com/git-for-windows/build-extra/blob/ab941145aeef/shears.sh#L12-L18

Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:

Well, I was not asking for postmortem of a particular breakage, per-se. Such a bug is well within the competent hands of GfW developer(s).

I was more interested in learning an improved process, e.g. giving you an advance notice of a few days so that you can do a practice run in the not-so-final-but-close-enough tip of the 'maint' branch to find out unexpected recent breakage either in the code or in your toolchain before the real release needs to be made in timely fashion, would have helped.

Thanks.