diff options
author | Johannes Sixt <j6t@kdbg.org> | 2009-03-13 23:35:24 +0100 |
---|---|---|
committer | Johannes Sixt <j6t@kdbg.org> | 2009-03-19 22:04:25 +0100 |
commit | 4114156ae959a8ecfea62213df35fd8f778d9c4e (patch) | |
tree | 36b01e53ac765961ad4fd71e8cf195ef38837a1b /t/t3400-rebase.sh | |
parent | test-lib: Work around missing sum on Windows (diff) | |
download | tgif-4114156ae959a8ecfea62213df35fd8f778d9c4e.tar.xz |
Tests on Windows: $(pwd) must return Windows-style paths
Many tests pass $(pwd) in some form to git and later test that the output
of git contains the correct value of $(pwd). For example, the test of
'git remote show' sets up a remote that contains $(pwd) and then the
expected result must contain $(pwd).
Again, MSYS-bash's path mangling kicks in: Plain $(pwd) uses the MSYS style
absolute path /c/path/to/git. The test case would write this name into
the 'expect' file. But when git is invoked, MSYS-bash converts this name to
the Windows style path c:/path/to/git, and git would produce this form in
the result; the test would fail.
We fix this by passing -W to bash's pwd that produces the Windows-style
path.
There are a two cases that need an accompanying change:
- In t1504 the value of $(pwd) becomes part of a path list. In this case,
the lone 'c' in something like /foo:c:/path/to/git:/bar inhibits
MSYS-bashes path mangling; IOW in this case we want the /c/path/to/git
form to allow path mangling. We use $PWD instead of $(pwd), which always
has the latter form.
- In t6200, $(pwd) - the Windows style path - must be used to construct the
expected result because that is the path form that git sees. (The change
in the test itself is just for consistency: 'git fetch' always sees the
Windows-style path, with or without the change.)
Signed-off-by: Johannes Sixt <j6t@kdbg.org>
Diffstat (limited to 't/t3400-rebase.sh')
0 files changed, 0 insertions, 0 deletions