From 511d1c355a683c3901d53b87723ba5382595bb59 Mon Sep 17 00:00:00 2001 From: Peter Kasting Date: Thu, 11 Jul 2024 12:54:43 -0700 Subject: [PATCH] Clarify release notes around issue #907. Notes workaround downside and explicitly states that no one is working on this, hence the bug closure. Signed-off-by: Peter Kasting --- ReleaseNotes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ReleaseNotes.md b/ReleaseNotes.md index 417c93ee75..660d0e6441 100644 --- a/ReleaseNotes.md +++ b/ReleaseNotes.md @@ -23,7 +23,7 @@ See [http://git-scm.com/](http://git-scm.com/) for further details about Git inc * As Git for Windows is shipped without Python support, `git p4` (which is backed by a Python script) is not supported. * The Quick Launch icon will only be installed for the user running setup (typically the Administrator). This is a technical restriction and will not change. * Git command hints are designed for a POSIX shell, this can lead to issues when using them **as is** in non-POSIX shells like PowerShell, [as is the case in this ticket](https://github.com/git-for-windows/git/issues/2785). -* When pushing via the `git://` protocol, Git for Windows may hang indefinitely. The last console output in this case is typically `Writing objects: 100%`. Until issue [#907](https://github.com/git-for-windows/git/issues/907) is addressed, run this command once as a work-around: `git config sendpack.sideband false`. +* When pushing via the `git://` protocol, Git for Windows may hang indefinitely. The last console output in this case is typically `Writing objects: 100%`. As a workaround, disabling side-band via `git config sendpack.sideband false` should address this, at the cost of showing remote errors late (or not at all). No one is working on this; for more details, or to contribute a fix, see issue [#907](https://github.com/git-for-windows/git/issues/907) (closed unless/until there is activity). * Git for Windows executables linked to `msys-2.0.dll` are not compatible with Mandatory ASLR and may crash if system-wide Mandatory ASLR is enabled in Windows Exploit protection. A workaround is to disable ASLR for all executables in `C:\Program Files\Git\usr\bin`, run in administrator powershell (replace `$_.Name` with `$_` to use full path to executable instead of name): > `Get-Item -Path "C:\Program Files\Git\usr\bin\*.exe" | %{ Set-ProcessMitigation -Name $_.Name -Disable ForceRelocateImages }`