| commit | 3cc6a6f0f7519733deeebe17d7a19a53e9c02028 | |
| author | Jeff King <peff@peff.net> | |
| Thu, 20 Mar 2014 23:15:24 +0000 (20 19:15 -0400) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Fri, 21 Mar 2014 21:24:40 +0000 (21 14:24 -0700) | ||
| tree | c5275731de7191529cd82e6faffcb2fbd7ae9edd | treesnapshot (tar.gz zip) |
| parent | 221bf985063737240124fe15c328cd125e9d048e | commitdiff |
t: stop using GIT_CONFIG to cross repo boundaries
Some tests want to check or set config in another
repository. E.g., t1000 creates repositories and makes sure
that their core.bare and core.worktree settings are what we
expect. We can do this with:
GIT_CONFIG=$repo/.git/config git config ...
but it better shows the intent to just enter the repository
and let "git config" do the normal lookups:
(cd $repo && git config ...)
In theory, this would cause us to use an extra subshell, but
in all such cases, we are actually already in a subshell.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Some tests want to check or set config in another
repository. E.g., t1000 creates repositories and makes sure
that their core.bare and core.worktree settings are what we
expect. We can do this with:
GIT_CONFIG=$repo/.git/config git config ...
but it better shows the intent to just enter the repository
and let "git config" do the normal lookups:
(cd $repo && git config ...)
In theory, this would cause us to use an extra subshell, but
in all such cases, we are actually already in a subshell.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| t/t0001-init.sh | diffblobblamehistory | |
| t/t5701-clone-local.sh | diffblobblamehistory |