diff options
author | Jeff King <peff@peff.net> | 2016-05-13 16:47:24 -0400 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2016-05-14 10:37:29 -0700 |
commit | 9874576995c8ecf800e48dead0e34c36defa91b4 (patch) | |
tree | bfcc6678dc921e73141f2b177480e9236aa7e0f1 /builtin/mailinfo.c | |
parent | t9107: use "return 1" instead of "exit 1" (diff) | |
download | tgif-9874576995c8ecf800e48dead0e34c36defa91b4.tar.xz |
t9107: switch inverted single/double quotes in test
One of the test snippets in t9107 is enclosed in double
quotes, but then uses single quotes to surround an
interpolated variable inside the snippet, like:
test_expect_success '...' "
test -n '$head'
"
This happens to work because the variable is interpolated
_before_ the snippet is run, and the result is eval'd. So as
long as the variable does not contain any single quotes, the
two are equivalent. And it doesn't, as we know it is a sha1
from rev-parse above. But this construct is unnecessarily
confusing.
But we can go a step further in cleaning up. The test is
really checking that a particular ref has a value. Rather
than checking if rev-parse produced output, we can just move
rev-parse into the test itself, and rely on the exit code
from --verify. Nobody else cares about the $head variable at
all.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'builtin/mailinfo.c')
0 files changed, 0 insertions, 0 deletions