From: AbdAlRahman Gad <abdobngad@gmail.com>
To: Eric Sunshine <sunshine@sunshineco.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v3 4/6] [Newcomer] t7004-tag: do not prepare except outside test_expect_success
Date: Sun, 4 Aug 2024 12:01:14 +0300 [thread overview]
Message-ID: <a3d28946-2ec1-4388-8eab-0ac0c5298cf6@gmail.com> (raw)
In-Reply-To: <CAPig+cSAG4hcLRg9nAg7JGssm5Eh87-z4kWSu_RLgJZuzhyX8w@mail.gmail.com>
On 8/4/24 10:32 AM, Eric Sunshine wrote:
> On Sun, Aug 4, 2024 at 3:12 AM AbdAlRahman Gad <abdobngad@gmail.com> wrote:
>> do not prepare expect outside test_expect_success
>>
>> Signed-off-by: AbdAlRahman Gad <abdobngad@gmail.com>
>> ---
>> diff --git a/t/t7004-tag.sh b/t/t7004-tag.sh
>> @@ -131,10 +131,10 @@ test_expect_success 'listing all tags if one exists should succeed' '
>> -cat >expect <<EOF
>> -mytag
>> -EOF
>> test_expect_success 'Multiple -l or --list options are equivalent to one -l option' '
>> + cat >expect <<-\EOF &&
>> + mytag
>> + EOF
>> git tag -l -l >actual &&
>
> This patch also changes bare `EOF` to `\EOF` which correctly signals
> to the reader that no variable interpolation or other processing is
> happening inside the here-doc body. Such a change of semantics is
> significant enough that it normally warrants mention in the commit
> message. In fact, often the `EOF` to `\EOF` change would be done in
> its own commit. However, it's probably not worth a reroll in this
> case; v3 is likely a good place to stop unless a reviewer finds a
> problem which demands v4.
Thanks for the feedback.
I'll keep that in mind in the upcoming patches.
next prev parent reply other threads:[~2024-08-04 9:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-04 7:11 [PATCH v3 0/6] [Newcomer] t7004: modernize the style AbdAlRahman Gad
2024-08-04 7:11 ` [PATCH v3 1/6] [Newcomer] t7004-tag: redirection operator AbdAlRahman Gad
2024-08-05 9:36 ` Patrick Steinhardt
2024-08-04 7:11 ` [PATCH v3 2/6] [Newcomer] t7004-tag: do not lose exit status to pipe AbdAlRahman Gad
2024-08-05 9:36 ` Patrick Steinhardt
2024-08-04 7:11 ` [PATCH v3 3/6] [Newcomer] t7004-tag: one command per line AbdAlRahman Gad
2024-08-05 9:36 ` Patrick Steinhardt
2024-08-04 7:11 ` [PATCH v3 4/6] [Newcomer] t7004-tag: do not prepare except outside test_expect_success AbdAlRahman Gad
2024-08-04 7:32 ` Eric Sunshine
2024-08-04 9:01 ` AbdAlRahman Gad [this message]
2024-08-04 16:46 ` Junio C Hamano
2024-08-04 7:11 ` [PATCH v3 5/6] [Newcomer] t7004-tag: here-doc modernization AbdAlRahman Gad
2024-08-05 9:42 ` Patrick Steinhardt
2024-08-04 7:11 ` [PATCH v3 6/6] [Newcomer] t7004-tag: description on the same line as test_expect_success AbdAlRahman Gad
2024-08-05 9:42 ` Patrick Steinhardt
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=a3d28946-2ec1-4388-8eab-0ac0c5298cf6@gmail.com \
--to=abdobngad@gmail.com \
--cc=git@vger.kernel.org \
--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 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).