2018-09-16 10:50:02 +03:00
|
|
|
#!/bin/sh
|
|
|
|
|
|
|
|
test_description='git command aliasing'
|
|
|
|
|
|
|
|
. ./test-lib.sh
|
|
|
|
|
|
|
|
test_expect_success 'nested aliases - internal execution' '
|
|
|
|
git config alias.nested-internal-1 nested-internal-2 &&
|
|
|
|
git config alias.nested-internal-2 status &&
|
|
|
|
git nested-internal-1 >output &&
|
|
|
|
test_i18ngrep "^On branch " output
|
|
|
|
'
|
|
|
|
|
|
|
|
test_expect_success 'nested aliases - mixed execution' '
|
|
|
|
git config alias.nested-external-1 nested-external-2 &&
|
|
|
|
git config alias.nested-external-2 "!git nested-external-3" &&
|
|
|
|
git config alias.nested-external-3 status &&
|
|
|
|
git nested-external-1 >output &&
|
|
|
|
test_i18ngrep "^On branch " output
|
|
|
|
'
|
|
|
|
|
|
|
|
test_expect_success 'looping aliases - internal execution' '
|
|
|
|
git config alias.loop-internal-1 loop-internal-2 &&
|
|
|
|
git config alias.loop-internal-2 loop-internal-3 &&
|
|
|
|
git config alias.loop-internal-3 loop-internal-2 &&
|
|
|
|
test_must_fail git loop-internal-1 2>output &&
|
|
|
|
test_i18ngrep "^fatal: alias loop detected: expansion of" output
|
|
|
|
'
|
|
|
|
|
|
|
|
# This test is disabled until external loops are fixed, because would block
|
|
|
|
# the test suite for a full minute.
|
|
|
|
#
|
|
|
|
#test_expect_failure 'looping aliases - mixed execution' '
|
|
|
|
# git config alias.loop-mixed-1 loop-mixed-2 &&
|
|
|
|
# git config alias.loop-mixed-2 "!git loop-mixed-1" &&
|
|
|
|
# test_must_fail git loop-mixed-1 2>output &&
|
|
|
|
# test_i18ngrep "^fatal: alias loop detected: expansion of" output
|
|
|
|
#'
|
|
|
|
|
2019-10-07 22:38:56 +03:00
|
|
|
test_expect_success 'run-command formats empty args properly' '
|
2020-06-02 13:12:25 +03:00
|
|
|
test_must_fail env GIT_TRACE=1 git frotz a "" b " " c 2>actual.raw &&
|
mingw: when path_lookup() failed, try BusyBox
BusyBox comes with a ton of applets ("applet" being the identical
concept to Git's "builtins"). And similar to Git's builtins, the applets
can be called via `busybox <command>`, or the BusyBox executable can be
copied/hard-linked to the command name.
The similarities do not end here. Just as with Git's builtins, it is
problematic that BusyBox' hard-linked applets cannot easily be put into
a .zip file: .zip archives have no concept of hard-links and therefore
would store identical copies (and also extract identical copies,
"inflating" the archive unnecessarily).
To counteract that issue, MinGit already ships without hard-linked
copies of the builtins, and the plan is to do the same with BusyBox'
applets: simply ship busybox.exe as single executable, without
hard-linked applets.
To accommodate that, Git is being taught by this commit a very special
trick, exploiting the fact that it is possible to call an executable
with a command-line whose argv[0] is different from the executable's
name: when `sh` is to be spawned, and no `sh` is found in the PATH, but
busybox.exe is, use that executable (with unchanged argv).
Likewise, if any executable to be spawned is not on the PATH, but
busybox.exe is found, parse the output of `busybox.exe --help` to find
out what applets are included, and if the command matches an included
applet name, use busybox.exe to execute it.
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
2017-07-20 21:41:29 +03:00
|
|
|
sed -ne "/run_command: git-frotz/s/.*trace: run_command: //p" actual.raw >actual &&
|
2020-06-02 13:12:25 +03:00
|
|
|
echo "git-frotz a '\'''\'' b '\'' '\'' c" >expect &&
|
|
|
|
test_cmp expect actual
|
2019-10-07 22:38:56 +03:00
|
|
|
'
|
|
|
|
|
2018-09-16 10:50:02 +03:00
|
|
|
test_done
|