All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Lehmann <Jens.Lehmann@web.de>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH] tests: use test_cmp instead of piping to diff(1)
Date: Wed, 15 Sep 2010 01:17:51 +0200	[thread overview]
Message-ID: <4C90029F.6020909@web.de> (raw)
In-Reply-To: <AANLkTinGt6d8tKh8yOT0SJpcgsv+KgrE4jPT2_RgGzeG@mail.gmail.com>

Am 14.09.2010 03:45, schrieb Ævar Arnfjörð Bjarmason:
> On Mon, Sep 13, 2010 at 23:31, Junio C Hamano <gitster@pobox.com> wrote:
>> Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:
>>
>>> @@ -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
>>>  "
>>
>> Nit.  Did you really mean <<-EOF, not <<EOF, here, especially you are
>> writing the here document without indentation with any TAB?
> 
> I just meant to replace the diff invocations with test_cmp. Changing
> the surrounding here-docs was outside the scope of the patch.

I plead guilty for introducing the "<<-EOF"s in the first place by
simply copying the frame for this test from t7401. But me too thinks
the "test_cmp" should have TABs in front of them instead of spaces.

With the "TAB in front of test_cmp" issue fixed you may add:
Acked-by: Jens Lehmann <Jens.Lehmann@web.de>

  reply	other threads:[~2010-09-14 23:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-13 20:59 [PATCH] tests: use test_cmp instead of piping to diff(1) Ævar Arnfjörð Bjarmason
2010-09-13 23:31 ` Junio C Hamano
2010-09-14  1:45   ` Ævar Arnfjörð Bjarmason
2010-09-14 23:17     ` Jens Lehmann [this message]
2010-09-15 23:15       ` Ævar Arnfjörð Bjarmason

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=4C90029F.6020909@web.de \
    --to=jens.lehmann@web.de \
    --cc=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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.