From: Johannes Sixt <j6t@xxxxxxxx> The bash on Windows rewrites paths that look like absolute POSIX paths when they are a command-line argument of a regular Windows program, such as git and the test helpers. As a consequence, the actual tests performed are not what the tests scripts expect. The tests that need *not* be skipped are those where the two paths passed to 'test-path-utils relative_path' have the same prefix and the result is expected to be a relative path. This is because the rewriting changes "/a/b" to "D:/Src/MSysGit/a/b", and when both inputs are extended the same way, this just cancels out in the relative path computation. Signed-off-by: Johannes Sixt <j6t@xxxxxxxx> --- t/t0060-path-utils.sh | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/t/t0060-path-utils.sh b/t/t0060-path-utils.sh index dfe4747..4deec52 100755 --- a/t/t0060-path-utils.sh +++ b/t/t0060-path-utils.sh @@ -190,15 +190,15 @@ test_expect_success SYMLINKS 'real path works on symlinks' ' relative_path /a/b/c/ /a/b/ c/ relative_path /a/b/c/ /a/b c/ -relative_path /a//b//c/ //a/b// c/ +relative_path /a//b//c/ //a/b// c/ POSIX relative_path /a/b /a/b ./ relative_path /a/b/ /a/b ./ relative_path /a /a/b ../ relative_path / /a/b/ ../../ relative_path /a/c /a/b/ ../c relative_path /a/c /a/b ../c -relative_path /a/b "<empty>" /a/b -relative_path /a/b "<null>" /a/b +relative_path /a/b "<empty>" /a/b POSIX +relative_path /a/b "<null>" /a/b POSIX relative_path "<empty>" /a/b ./ relative_path "<empty>" "<empty>" ./ relative_path "<empty>" "<null>" ./ -- 1.8.3.1.1670.g1dbc49e -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html