From: David Aguilar <davvid@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Charles Bailey <charles@hashpling.org>,
Thomas Rast <trast@student.ethz.ch>
Subject: [PATCH v2 4/5] t7610-mergetool: use test_config to isolate tests
Date: Wed, 15 Oct 2014 22:30:04 -0700 [thread overview]
Message-ID: <1413437404-23810-1-git-send-email-davvid@gmail.com> (raw)
In-Reply-To: <xmqqwq81ujlw.fsf@gitster.dls.corp.google.com>
Signed-off-by: David Aguilar <davvid@gmail.com>
---
This is a replacement patch for
"t7610-mergetool: prefer test_config over git config"
in da/mergetool-tests.
Changes since v1:
The changes are more surgical and the commit message mentions
why we are using test_config.
t/t7610-mergetool.sh | 8 +++-----
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git a/t/t7610-mergetool.sh b/t/t7610-mergetool.sh
index 1a15e06..4fec633 100755
--- a/t/t7610-mergetool.sh
+++ b/t/t7610-mergetool.sh
@@ -112,7 +112,7 @@ test_expect_success 'custom mergetool' '
'
test_expect_success 'mergetool crlf' '
- git config core.autocrlf true &&
+ test_config core.autocrlf true &&
git checkout -b test2 branch1 &&
test_must_fail git merge master >/dev/null 2>&1 &&
( yes "" | git mergetool file1 >/dev/null 2>&1 ) &&
@@ -505,14 +505,12 @@ test_expect_success 'file with no base' '
test_expect_success 'custom commands override built-ins' '
git checkout -b test14 branch1 &&
- git config mergetool.defaults.cmd "cat \"\$REMOTE\" >\"\$MERGED\"" &&
- git config mergetool.defaults.trustExitCode true &&
+ test_config mergetool.defaults.cmd "cat \"\$REMOTE\" >\"\$MERGED\"" &&
+ test_config mergetool.defaults.trustExitCode true &&
test_must_fail git merge master &&
git mergetool --no-prompt --tool defaults -- both &&
echo master both added >expected &&
test_cmp both expected &&
- git config --unset mergetool.defaults.cmd &&
- git config --unset mergetool.defaults.trustExitCode &&
git reset --hard master >/dev/null 2>&1
'
--
2.1.2.453.g1b015e3
prev parent reply other threads:[~2014-10-16 5:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-15 8:35 [PATCH 1/5] t7610-mergetool: use tabs instead of a mix of tabs and spaces David Aguilar
2014-10-15 8:35 ` [PATCH 2/5] t7610-mergetool: add missing && and remove commented-out code David Aguilar
2014-10-15 8:35 ` [PATCH 3/5] t7610-mergetool: add test cases for mergetool.writeToTemp David Aguilar
2014-10-15 8:35 ` [PATCH 4/5] t7610-mergetool: prefer test_config over git config David Aguilar
2014-10-15 8:35 ` [PATCH 5/5] test-lib-functions: adjust style to match CodingGuidelines David Aguilar
2014-10-15 21:08 ` [PATCH 4/5] t7610-mergetool: prefer test_config over git config Junio C Hamano
2014-10-16 5:30 ` David Aguilar [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1413437404-23810-1-git-send-email-davvid@gmail.com \
--to=davvid@gmail.com \
--cc=charles@hashpling.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=trast@student.ethz.ch \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).