summaryrefslogtreecommitdiff
path: root/t/t3020-ls-files-error-unmatch.sh
diff options
context:
space:
mode:
authorLibravatar Elijah Newren <newren@gmail.com>2021-12-09 05:08:26 +0000
committerLibravatar Junio C Hamano <gitster@pobox.com>2021-12-09 13:33:12 -0800
commite6f8861bd43636b27651150e6a3caa0a937fb418 (patch)
tree5e34dc20fe1f1414bb592b4bbc5d1164587e88c4 /t/t3020-ls-files-error-unmatch.sh
parentt2501: add various tests for removing the current working directory (diff)
downloadtgif-e6f8861bd43636b27651150e6a3caa0a937fb418.tar.xz
setup: introduce startup_info->original_cwd
Removing the current working directory causes all subsequent git commands run from that directory to get confused and fail with a message about being unable to read the current working directory: $ git status fatal: Unable to read current working directory: No such file or directory Non-git commands likely have similar warnings or even errors, e.g. $ bash -c 'echo hello' shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory hello This confuses end users, particularly since the command they get the error from is not the one that caused the problem; the problem came from the side-effect of some previous command. We would like to avoid removing the current working directory of our parent process; towards this end, introduce a new variable, startup_info->original_cwd, that tracks the current working directory that we inherited from our parent process. For convenience of later comparisons, we prefer that this new variable store a path relative to the toplevel working directory (thus much like 'prefix'), except without the trailing slash. Subsequent commits will make use of this new variable. Acked-by: Derrick Stolee <stolee@gmail.com> Acked-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com> Signed-off-by: Elijah Newren <newren@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t3020-ls-files-error-unmatch.sh')
0 files changed, 0 insertions, 0 deletions