diff options
author | Johannes Schindelin <johannes.schindelin@gmx.de> | 2024-07-13 21:08:22 +0000 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2024-07-13 16:23:37 -0700 |
commit | 92fe7c7d42cc941ed70d6fce988d6b7936a9765a (patch) | |
tree | f1d4d4b4643d4f8cb01a6f1a7d9a63cc770d19a3 /builtin/commit.c | |
parent | f1ed769a3bc045d9f79396fb6074bfb33b83e09d (diff) |
run-command(win32): resolve the path to the Unix shell early
In 776297548e (Do not use SHELL_PATH from build system in
prepare_shell_cmd on Windows, 2012-04-17), the hard-coded path to the
Unix shell was replaced by passing `sh` instead when executing Unix
shell scripts in Git.
This was done because the hard-coded path to the Unix shell is incorrect
on Windows because it not only is a Unix-style absolute path instead of
a Windows one, but Git uses the runtime prefix feature on Windows, i.e.
the correct path cannot be hard-coded.
Naturally, the `sh` argument will be resolved to the full path of said
executable eventually.
To help fixing the bug where `git var GIT_SHELL_PATH` currently does not
reflect that logic, but shows that incorrect hard-coded Unix-style
absolute path, let's resolve the full path to the `sh` executable early
in the `git_shell_path()` function so that we can use it in `git var`,
too, and be sure that the output is equivalent to what `run_command()`
does when it is asked to execute a command-line using a Unix shell.
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'builtin/commit.c')
0 files changed, 0 insertions, 0 deletions