From: Junio C Hamano <gitster@pobox.com>
To: Patrick Steinhardt <ps@pks.im>
Cc: git@vger.kernel.org, "SZEDER Gábor" <szeder.dev@gmail.com>
Subject: Re: [PATCH v2 0/3] t7800: fix quoting of looped test bodies
Date: Fri, 22 Mar 2024 07:37:43 -0700 [thread overview]
Message-ID: <xmqqmsqq49jc.fsf@gitster.g> (raw)
In-Reply-To: <cover.1711074118.git.ps@pks.im> (Patrick Steinhardt's message of "Fri, 22 Mar 2024 03:23:32 +0100")
Patrick Steinhardt <ps@pks.im> writes:
> Hi,
>
> this is the second version of my patch series that aims to address some
> issues with looping around `test_expect_success` in t7800.
Looking good. Thanks. Will queue.
Let's mark it for 'next' already ;-)
>
> Changes compared to v1:
>
> - Fixed indentation of a paragraph in "t/README".
>
> - Added a clarification why one wants to use single quotes to
> "t/README".
>
> Thanks!
>
> Patrick
>
> Patrick Steinhardt (3):
> t7800: improve test descriptions with empty arguments
> t7800: use single quotes for test bodies
> t/README: document how to loop around test cases
>
> t/README | 20 ++++++++++++++++++++
> t/t7800-difftool.sh | 40 ++++++++++++++++++++--------------------
> 2 files changed, 40 insertions(+), 20 deletions(-)
>
> Range-diff against v1:
> 1: fd37c29319 = 1: fd37c29319 t7800: improve test descriptions with empty arguments
> 2: a4ca974397 = 2: a4ca974397 t7800: use single quotes for test bodies
> 3: 326fb79650 ! 3: f83b710208 t/README: document how to loop around test cases
> @@ t/README: The "do's:"
> + '
> + done
> +
> -+ Note that while the test title uses double quotes ("), the test body
> -+ should continue to use single quotes ('). The loop variable will be
> -+ accessible regardless of the single quotes as the test body is passed
> -+ to `eval`.
> ++ Note that while the test title uses double quotes ("), the test body
> ++ should continue to use single quotes (') to avoid breakage in case the
> ++ values contain e.g. quoting characters. The loop variable will be
> ++ accessible regardless of the single quotes as the test body is passed
> ++ to `eval`.
> +
>
> And here are the "don'ts:"
prev parent reply other threads:[~2024-03-22 14:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-21 13:47 [PATCH 0/3] t7800: fix quoting of looped test bodies Patrick Steinhardt
2024-03-21 13:47 ` [PATCH 1/3] t7800: improve test descriptions with empty arguments Patrick Steinhardt
2024-03-21 13:47 ` [PATCH 2/3] t7800: use single quotes for test bodies Patrick Steinhardt
2024-03-21 13:47 ` [PATCH 3/3] t/README: document how to loop around test cases Patrick Steinhardt
2024-03-21 17:12 ` Junio C Hamano
2024-03-22 2:05 ` Patrick Steinhardt
2024-03-22 2:12 ` Junio C Hamano
2024-03-21 13:48 ` [PATCH 0/3] t7800: fix quoting of looped test bodies Patrick Steinhardt
2024-03-22 2:23 ` [PATCH v2 " Patrick Steinhardt
2024-03-22 2:23 ` [PATCH v2 1/3] t7800: improve test descriptions with empty arguments Patrick Steinhardt
2024-03-22 2:23 ` [PATCH v2 2/3] t7800: use single quotes for test bodies Patrick Steinhardt
2024-03-22 2:23 ` [PATCH v2 3/3] t/README: document how to loop around test cases Patrick Steinhardt
2024-03-22 14:37 ` Junio C Hamano [this message]
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=xmqqmsqq49jc.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=ps@pks.im \
--cc=szeder.dev@gmail.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 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).