t: prefer "git config --file" to GIT_CONFIG
Doing: GIT_CONFIG=foo git config ... is equivalent to: git config --file=foo ... The latter is easier to read and slightly less error-prone, because of issues with one-shot variables and shell functions (e.g., you cannot use the former with test_must_fail). Note that we explicitly leave one case in t1300 which checks the same operation on both GIT_CONFIG and "git config --file". They are equivalent in the code these days, but this will make sure it remains so. Signed-off-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
This commit is contained in:
committed by
Junio C Hamano
parent
551a3e60d1
commit
f7e8714101
@ -249,8 +249,7 @@ test_expect_success 'submodule add in subdirectory with relative path should fai
|
||||
'
|
||||
|
||||
test_expect_success 'setup - add an example entry to .gitmodules' '
|
||||
GIT_CONFIG=.gitmodules \
|
||||
git config submodule.example.url git://example.com/init.git
|
||||
git config --file=.gitmodules submodule.example.url git://example.com/init.git
|
||||
'
|
||||
|
||||
test_expect_success 'status should fail for unmapped paths' '
|
||||
@ -264,7 +263,7 @@ test_expect_success 'setup - map path in .gitmodules' '
|
||||
path = init
|
||||
EOF
|
||||
|
||||
GIT_CONFIG=.gitmodules git config submodule.example.path init &&
|
||||
git config --file=.gitmodules submodule.example.path init &&
|
||||
|
||||
test_cmp expect .gitmodules
|
||||
'
|
||||
|
||||
Reference in New Issue
Block a user