From: Jonathan Nieder <jrnieder@gmail.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>,
Johannes Sixt <j.sixt@viscovery.net>
Subject: Re: [PATCH 3/4] tests: use test_cmp instead of piping to diff(1)
Date: Sun, 14 Nov 2010 11:41:33 -0600 [thread overview]
Message-ID: <20101114174133.GD26459@burratino> (raw)
In-Reply-To: <1289745857-16704-4-git-send-email-avarab@gmail.com>
Ævar Arnfjörð Bjarmason wrote:
> --- a/t/t4041-diff-submodule-option.sh
> +++ b/t/t4041-diff-submodule-option.sh
> @@ -37,9 +37,10 @@ head1=$(add_file sm1 foo1 foo2)
> test_expect_success 'added submodule' "
> git add sm1 &&
> git diff-index -p --submodule=log HEAD >actual &&
> - diff actual - <<-EOF
> + cat >expected <<-EOF &&
> Submodule sm1 0000000...$head1 (new submodule)
> EOF
> + test_cmp expected actual
> "
Nice. Reminds me of
http://thread.gmane.org/gmane.comp.version-control.git/160168/focus=160222
(use of "cmp - foo.expect" in git svn tests); anyone want to take a
stab at fixing that, too?
> --- a/t/t7401-submodule-summary.sh
> +++ b/t/t7401-submodule-summary.sh
[...]
> test_expect_success '--for-status' "
> git submodule summary --for-status HEAD^ >actual &&
> - test_cmp actual - <<EOF
> + test_cmp actual - <<EOF
I think this tab should be spaces? Also, shouldn't this be
cat >expect <<EOF &&
...
EOF
test_cmp expect actual
to match the others? There are a few similar cases in the patch.
I assume you've checked the patched tests still pass. So with the exception
just mentioned,
Reviewed-by: Jonathan Nieder <jrnieder@gmail.com>
Thanks.
next prev parent reply other threads:[~2010-11-14 17:42 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-14 14:44 [PATCH 0/4] [PULL] ab/i18n-prereqs, prerequisites for ab/i18n Ævar Arnfjörð Bjarmason
2010-11-14 14:44 ` [PATCH 1/4] Makefile: move "Platform specific tweaks" above LIB_{H,OBJS} Ævar Arnfjörð Bjarmason
2010-11-14 17:23 ` Jonathan Nieder
2010-11-14 17:51 ` Ævar Arnfjörð Bjarmason
2010-11-14 18:51 ` Jonathan Nieder
2010-11-15 16:07 ` Junio C Hamano
2010-11-15 16:11 ` Jonathan Nieder
2010-11-15 16:16 ` Ævar Arnfjörð Bjarmason
2010-11-14 19:12 ` Junio C Hamano
2010-11-14 17:53 ` Jonathan Nieder
2010-11-14 19:08 ` Junio C Hamano
2010-11-14 14:44 ` [PATCH 2/4] t7004-tag.sh: re-arrange git tag comment for clarity Ævar Arnfjörð Bjarmason
2010-11-14 17:32 ` Jonathan Nieder
2010-11-14 17:57 ` Ævar Arnfjörð Bjarmason
2010-11-14 14:44 ` [PATCH 3/4] tests: use test_cmp instead of piping to diff(1) Ævar Arnfjörð Bjarmason
2010-11-14 17:41 ` Jonathan Nieder [this message]
2010-11-14 14:44 ` [PATCH 4/4] builtin: use builtin.h for all builtin commands Ævar Arnfjörð Bjarmason
2010-11-14 15:01 ` Sverre Rabbelier
2010-11-14 15:11 ` Ævar Arnfjörð Bjarmason
2010-11-14 18:55 ` Junio C Hamano
2010-11-14 17:47 ` Jonathan Nieder
2010-11-17 19:54 ` Junio C Hamano
2010-11-17 20:08 ` Ævar Arnfjörð Bjarmason
2010-11-17 20:15 ` Jonathan Nieder
2010-11-14 17:50 ` [PATCH 0/4] [PULL] ab/i18n-prereqs, prerequisites for ab/i18n Jonathan Nieder
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=20101114174133.GD26459@burratino \
--to=jrnieder@gmail.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j.sixt@viscovery.net \
/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).