Release Notes: announce that 32-bit support is about to be deprecated

Since Git for Windows relies on the MSYS2 runtime for POSIX emulation as required e.g. by the Bash (which is used by Git to execute aliases, hooks, and the `git submodule` command), and since the MSYS2 project already dropped support for the i686 variant of the MSYS2 runtime (following Cygwin's lead), Git for Windows won't be able to provide full support of 32-bit installers going forward. Let's warn the users about this. Signed-off-by: Johannes Schindelin <[email protected]>
git-for-windows · Feb 21, 2023 · eefa7e4 · eefa7e4
1 parent 89ecfaf
commit eefa7e4
Showing 1 changed file with 2 additions and 0 deletions.
diff --git a/ReleaseNotes.md b/ReleaseNotes.md
@@ -44,6 +44,8 @@ This package contains software from a number of other projects including Bash, z
 
 As announced previously, Git for Windows will drop support for Windows 7 and for Windows 8 in one of the next versions, following [Cygwin's and MSYS2's lead](https://www.msys2.org/docs/windows_support/) (Git for Windows relies on MSYS2 for components such as Bash and Perl).
 
+Also following the footsteps of the MSYS2 and Cygwin projects on which Git for Windows depends, the 32-bit variant of Git for Windows [is nearing its end of support](https://gitforwindows.org/32-bit.html).
+
 ### New Features
 
 * In the olden Git days, there were "dashed" Git commands (e.g. `git-commit` instead of `git commit`). These haven't been supported for interactive use in a really, really long time. But they still worked in Git aliases and hooks ("scripts"). Since Git v1.5.4 (released on February 2nd, 2008), it was discouraged/deprecated to use dashed Git commands even in scripts. As of this version, Git for Windows [no longer supports these dashed commands](https://github.com/git-for-windows/git/pull/4252).