Allow GIT_CONFIG_GLOBAL to be set to NUL (all upper-case) - #6450
Merged
dscho merged 1 commit intoOct 1, 2026
Merged
Conversation
The special-casing of `NUL` in `mingw_access()` was added in 9160068 (msvc: avoid calling `access("NUL", flags)`, 2021-04-16) because the Universal C Runtime's ("UCRT") `_waccess()` rejects `NUL` as an invalid argument. With the switch of GIt for Windows from the MSVCRT-based MINGW64 build to the UCRT-based UCRT64 build in 2.56.0, any spelling other than lowercase `nul` now reaches `_waccess()` and fails. Windows device names are case-insensitive, and `NUL` is the canonical spelling, but even `Nul` is allowed, so a case-insensitive comparison is needed. Note that we cannot use `fspathcmp()` here, as we would usually do: This function is in the code path when reading the config, and `core.ignoreCase` would therefore not be set correctly yet e.g. when running under `GIT_CONFIG_GLOBAL=NUL`. This fixes git-for-windows#6449 Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Member
Author
|
/snapshot The |
mjcheetham
approved these changes
Sep 29, 2026
Validate the installer manuallyThe installer was built successfully; |
Member
Author
|
/add relnote bug Suppressing the user-wide Git config via The workflow run was started |
github-actions Bot
pushed a commit
to git-for-windows/build-extra
that referenced
this pull request
Sep 30, 2026
![gitforwindowshelper[bot]](https://github.githubassets.com/images/gravatars/gravatar-user-420.png){kind=avatar}
Suppressing the user-wide Git config via `GIT_CONFIG_GLOBAL=NUL` [was broken in v2.56.0](git-for-windows/git#6449) (surprisingly, as a consequence of the MINGW64 -> UCRT64 migration), which [was fixed](git-for-windows/git#6450). Signed-off-by: gitforwindowshelper[bot] <gitforwindowshelper-bot@users.noreply.github.com>
Member
Author
|
Before merging, I need to fix the failing |
3 tasks done
gitforwindowshelper Bot
pushed a commit
that referenced
this pull request
Oct 1, 2026
Currently, when running `GIT_CONFIG_GLOBAL=NUL git config --list`, it fails with: ``` fatal: unable to access 'NUL': Invalid argument ``` The underlying reason is the different behavior of the C runtime used by MINGW64 vs UCRT64. Let's accommodate for that. This fixes #6449
This was referenced Oct 1, 2026
gitforwindowshelper Bot
pushed a commit
that referenced
this pull request
Oct 1, 2026
Currently, when running `GIT_CONFIG_GLOBAL=NUL git config --list`, it fails with: ``` fatal: unable to access 'NUL': Invalid argument ``` The underlying reason is the different behavior of the C runtime used by MINGW64 vs UCRT64. Let's accommodate for that. This fixes #6449
gitforwindowshelper Bot
pushed a commit
that referenced
this pull request
Oct 1, 2026
Currently, when running `GIT_CONFIG_GLOBAL=NUL git config --list`, it fails with: ``` fatal: unable to access 'NUL': Invalid argument ``` The underlying reason is the different behavior of the C runtime used by MINGW64 vs UCRT64. Let's accommodate for that. This fixes #6449
This was referenced Oct 2, 2026
gitforwindowshelper Bot
pushed a commit
that referenced
this pull request
Oct 2, 2026
Currently, when running `GIT_CONFIG_GLOBAL=NUL git config --list`, it fails with: ``` fatal: unable to access 'NUL': Invalid argument ``` The underlying reason is the different behavior of the C runtime used by MINGW64 vs UCRT64. Let's accommodate for that. This fixes #6449
gitforwindowshelper Bot
pushed a commit
that referenced
this pull request
Oct 2, 2026
Currently, when running `GIT_CONFIG_GLOBAL=NUL git config --list`, it fails with: ``` fatal: unable to access 'NUL': Invalid argument ``` The underlying reason is the different behavior of the C runtime used by MINGW64 vs UCRT64. Let's accommodate for that. This fixes #6449
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Currently, when running
GIT_CONFIG_GLOBAL=NUL git config --list, it fails with:The underlying reason is the different behavior of the C runtime used by MINGW64 vs UCRT64. Let's accommodate for that.
This fixes #6449