From: Junio C Hamano <gitster@pobox.com>
To: Eric Sunshine <sunshine@sunshineco.com>
Cc: "Jeff King" <peff@peff.net>, "Git List" <git@vger.kernel.org>,
"Elijah Newren" <newren@gmail.com>,
"Shourya Shukla" <shouryashukla.oo@gmail.com>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Subject: Re: [PATCH v2] test_cmp: diagnose incorrect arguments
Date: Fri, 16 Oct 2020 16:14:31 -0700 [thread overview]
Message-ID: <xmqqy2k5931k.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <xmqqv9f9ao0v.fsf@gitster.c.googlers.com> (Junio C. Hamano's message of "Fri, 16 Oct 2020 13:56:00 -0700")
Junio C Hamano <gitster@pobox.com> writes:
> test_cmp() {
> - test $# -eq 2 || BUG "test_cmp requires two arguments"
> - if ! eval "$GIT_TEST_CMP" '"$@"'
> - then
> - test "x$1" = x- || test -e "$1" || BUG "test_cmp '$1' missing"
> - test "x$2" = x- || test -e "$2" || BUG "test_cmp '$2' missing"
> - return 1
> - fi
> + eval "$GIT_TEST_CMP" '"$@"'
> }
>
> # Check that the given config key has the expected value.
> @@ -940,13 +934,7 @@ test_cmp_config() {
> # test_cmp_bin - helper to compare binary files
>
> test_cmp_bin() {
> - test $# -eq 2 || BUG "test_cmp_bin requires two arguments"
> - if ! cmp "$@"
> - then
> - test "x$1" = x- || test -e "$1" || BUG "test_cmp_bin '$1' missing"
> - test "x$2" = x- || test -e "$2" || BUG "test_cmp_bin '$2' missing"
> - return 1
> - fi
> + cmp "$@"
> }
Looking at this again, I think we could keep the "we should have two
arguments, no more than, no less than, but exactly two". But I think
those who write new tests are working to eventually make them pass,
so hopefully they'll notice and investigate test_cmp that yields false
anyway, I guess.
next prev parent reply other threads:[~2020-10-16 23:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-09 6:08 [PATCH] test_cmp: diagnose incorrect arguments Eric Sunshine
2020-08-09 8:32 ` Shourya Shukla
2020-08-09 8:49 ` Eric Sunshine
2020-08-09 17:42 ` [PATCH v2] " Eric Sunshine
2020-08-09 19:12 ` Junio C Hamano
2020-08-09 19:34 ` Eric Sunshine
2020-08-10 15:22 ` Junio C Hamano
2020-08-11 18:32 ` Taylor Blau
2020-08-11 19:25 ` Eric Sunshine
2020-08-11 21:03 ` Taylor Blau
2020-08-12 15:37 ` Jeff King
2020-08-12 16:15 ` Eric Sunshine
2020-08-12 16:39 ` Eric Sunshine
2020-08-12 17:10 ` Jeff King
2020-10-16 0:17 ` Jeff King
2020-10-16 2:18 ` Eric Sunshine
2020-10-16 18:36 ` Junio C Hamano
2020-10-16 20:56 ` Junio C Hamano
2020-10-16 23:14 ` Junio C Hamano [this message]
2020-10-17 6:06 ` Eric Sunshine
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=xmqqy2k5931k.fsf@gitster.c.googlers.com \
--to=gitster@pobox.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=newren@gmail.com \
--cc=peff@peff.net \
--cc=shouryashukla.oo@gmail.com \
--cc=sunshine@sunshineco.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.