summaryrefslogtreecommitdiff
path: root/t/t1300-config-set.sh
diff options
context:
space:
mode:
authorJohannes Schindelin <johannes.schindelin@gmx.de>2022-01-19 18:56:01 (GMT)
committerJunio C Hamano <gitster@pobox.com>2022-01-19 19:27:31 (GMT)
commite2724c1ed1ca2605de6cf885bcfc4d512e93a537 (patch)
tree7d3815815c4c8d2ce4e88930b9bcc071c40e9e0a /t/t1300-config-set.sh
parentaf4e5f569bc89f356eb34a9373d7f82aca6faa8a (diff)
downloadgit-e2724c1ed1ca2605de6cf885bcfc4d512e93a537.zip
git-e2724c1ed1ca2605de6cf885bcfc4d512e93a537.tar.gz
git-e2724c1ed1ca2605de6cf885bcfc4d512e93a537.tar.bz2
getcwd(mingw): handle the case when there is no cwd
A recent upstream topic introduced checks for certain Git commands that prevent them from deleting the current working directory, introducing also a regression test that ensures that commands such as `git version` _can_ run without a current working directory. While technically not possible on Windows via the regular Win32 API, we do run the regression tests in an MSYS2 Bash which uses a POSIX emulation layer (the MSYS2/Cygwin runtime) where a really evil hack _does_ allow to delete a directory even if it is the current working directory. Therefore, Git needs to be prepared for a missing working directory, even on Windows. This issue was not noticed in upstream Git because there was no caller that tried to discover a Git directory with a deleted current working directory in the test suite. But in the microsoft/git fork, we do want to run `pre-command`/`post-command` hooks for every command, even for `git version`, which means that we make precisely such a call. The bug is not in that `pre-command`/`post-command` feature, though, but in `mingw_getcwd()` and needs to be addressed there. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t1300-config-set.sh')
0 files changed, 0 insertions, 0 deletions