| commit | 3e711a5314609621eea7a4c2ee1b7c02f5d0e542 | |
| author | Karl Wiberg <kha@treskal.com> | |
| Tue, 24 Sep 2013 23:26:08 +0000 (25 01:26 +0200) | ||
| committer | Karl Wiberg <kha@treskal.com> | |
| Tue, 24 Sep 2013 23:58:57 +0000 (25 01:58 +0200) | ||
| tree | 1b80e3db67390d395df131701f37926ee5dae003 | treesnapshot (tar.gz zip) |
| parent | 700eaba863f5a4aeb1d79d7f941cf2d033a33dec | commitdiff |
test-lib.sh: Don't set GIT_CONFIG to a relative path
If we do, things will fail if we call any git commands from a
subdirectory of a repository, where the relative path ".git/config"
isn't the path to the config file. The following tests are fixed by
this patch:
t1205-push-subdir.sh
t1800-import.sh
t2300-refresh-subdir.sh
t2800-goto-subdir.sh
I'm not sure why this used to work. I'm guessing git has gotten more
pedantic (which is a fine decision---if we give it the path to the
config file and that path doesn't work, we want it to fail!), but I
haven't attempted to verify this.
Signed-off-by: Karl Wiberg <kha@treskal.com>
If we do, things will fail if we call any git commands from a
subdirectory of a repository, where the relative path ".git/config"
isn't the path to the config file. The following tests are fixed by
this patch:
t1205-push-subdir.sh
t1800-import.sh
t2300-refresh-subdir.sh
t2800-goto-subdir.sh
I'm not sure why this used to work. I'm guessing git has gotten more
pedantic (which is a fine decision---if we give it the path to the
config file and that path doesn't work, we want it to fail!), but I
haven't attempted to verify this.
Signed-off-by: Karl Wiberg <kha@treskal.com>