From: Junio C Hamano <gitster@pobox.com>
To: Jerry Zhang <jerry@skydio.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH V2 1/2] patch-id: Fix antipatterns in tests
Date: Mon, 31 Jan 2022 15:36:43 -0800 [thread overview]
Message-ID: <xmqqfsp3h3zo.fsf@gitster.g> (raw)
In-Reply-To: <20220131232529.8484-1-jerry@skydio.com> (Jerry Zhang's message of "Mon, 31 Jan 2022 15:25:29 -0800")
Jerry Zhang <jerry@skydio.com> writes:
> test_expect_success 'patch-id handles no-nl-at-eof markers' '
> - cat nonl | calc_patch_id nonl &&
> - cat withnl | calc_patch_id withnl &&
> + cat >nonl <<-EOF &&
Unless you use $variable_expanded_to_its_value in the here-doc,
always make it a habit to quote the EOF marker. That helps the
readers by assuring that there is no funny interpolation going on.
> + diff --git i/a w/a
> + index e69de29..2e65efe 100644
> + --- i/a
> + +++ w/a
> + @@ -0,0 +1 @@
> + +a
> + \ No newline at end of file
> + diff --git i/b w/b
> + index e69de29..6178079 100644
> + --- i/b
> + +++ w/b
> + @@ -0,0 +1 @@
> + +b
> + EOF
> + cat >withnl <<-EOF &&
Likewise.
> + diff --git i/a w/a
> + index e69de29..7898192 100644
> + --- i/a
> + +++ w/a
> + @@ -0,0 +1 @@
> + +a
> + diff --git i/b w/b
> + index e69de29..6178079 100644
> + --- i/b
> + +++ w/b
> + @@ -0,0 +1 @@
> + +b
> + EOF
> + calc_patch_id nonl <nonl &&
> + calc_patch_id withnl <withnl &&
> test_cmp patch-id_nonl patch-id_withnl
> '
> test_done
next prev parent reply other threads:[~2022-01-31 23:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-31 23:23 [PATCH 1/2] format-patch: Fix antipatterns in tests Jerry Zhang
2022-01-31 23:23 ` [PATCH V3 2/2] patch-id: fix scan_hunk_header on diffs with 1 line of before/after Jerry Zhang
2022-01-31 23:52 ` [PATCH V4 " Jerry Zhang
2022-02-02 4:19 ` [PATCH V5 " Jerry Zhang
2022-01-31 23:25 ` [PATCH V2 1/2] patch-id: Fix antipatterns in tests Jerry Zhang
2022-01-31 23:36 ` Junio C Hamano [this message]
2022-01-31 23:52 ` [PATCH V3 " Jerry Zhang
2022-02-01 22:07 ` Johannes Sixt
2022-02-01 23:18 ` Junio C Hamano
2022-02-01 23:16 ` Junio C Hamano
2022-02-02 4:20 ` [PATCH V4 " Jerry Zhang
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=xmqqfsp3h3zo.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jerry@skydio.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.