diff options
author | Johannes Sixt <j6t@kdbg.org> | 2012-04-17 09:03:21 +0200 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2012-04-17 08:51:54 -0700 |
commit | 776297548e27d18edbd582a3cda599bb619668a9 (patch) | |
tree | 7ef94acb505112e3dc8d5b024641f0535c13d698 /Documentation/RelNotes/1.6.5.8.txt | |
parent | Use SHELL_PATH from build system in run_command.c:prepare_shell_cmd (diff) | |
download | tgif-776297548e27d18edbd582a3cda599bb619668a9.tar.xz |
Do not use SHELL_PATH from build system in prepare_shell_cmd on Windows
The recent change to use SHELL_PATH instead of "sh" to spawn shell commands
is not suited for Windows:
- The default setting, "/bin/sh", does not work when git has to run the
shell because it is a POSIX style path, but not a proper Windows style
path.
- If it worked, it would hard-code a position in the files system where
the shell is expected, making git (more precisely, the POSIX toolset that
is needed alongside git) non-relocatable. But we cannot sacrifice
relocatability on Windows.
- Apart from that, even though the Makefile leaves SHELL_PATH set to
"/bin/sh" for the Windows builds, the build system passes a mangled path
to the compiler, and something like "D:/Src/msysgit/bin/sh" is used,
which is doubly bad because it points to where /bin/sh resolves to on
the system where git was built.
- Finally, the system's CreateProcess() function that is used under
mingw.c's hood does not work with forward slashes and cannot find the
shell.
Undo the earlier change on Windows.
Signed-off-by: Johannes Sixt <j6t@kdbg.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation/RelNotes/1.6.5.8.txt')
0 files changed, 0 insertions, 0 deletions