From: Junio C Hamano <gitster@pobox.com>
To: "Strawbridge, Michael" <Michael.Strawbridge@amd.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>,
"Tuikov, Luben" <Luben.Tuikov@amd.com>
Subject: Re: [PATCH v5 2/2] send-email: expose header information to git-send-email's sendemail-validate hook
Date: Sat, 14 Jan 2023 19:34:17 -0800 [thread overview]
Message-ID: <xmqqfsccii86.fsf@gitster.g> (raw)
In-Reply-To: <xmqqa62lm76t.fsf@gitster.g> (Junio C. Hamano's message of "Sat, 14 Jan 2023 08:06:50 -0800")
Junio C Hamano <gitster@pobox.com> writes:
> Junio C Hamano <gitster@pobox.com> writes:
>
>> "Strawbridge, Michael" <Michael.Strawbridge@amd.com> writes:
>>
>>> +test_expect_success $PREREQ "--validate hook supports header argument" '
>>> + test_when_finished "rm my-hooks.ran" &&
>>> + write_script my-hooks/sendemail-validate <<-\EOF &&
>>> + filesize=$(stat -c%s "$2")
>>
>> That "stat -c" is a GNU-ism, I think. macOS CI jobs at GitHub do
>> not seem to like it.
>>
>>> + if [ "$filesize" != "0" ]; then
>>
>> Also, please see Documentation/CodingGuidelines to learn the subset
>> of shell script syntax and style we adopted for this project.
I'll tentatively queue this as a fix-up on top of the topic, but is
this testing the right thing? Should we inspect "$2" and verify
that it gives us what we expect, not just it being non-empty?
t/t9001-send-email.sh | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git c/t/t9001-send-email.sh w/t/t9001-send-email.sh
index f02b1eba16..b19997cbbc 100755
--- c/t/t9001-send-email.sh
+++ w/t/t9001-send-email.sh
@@ -568,9 +568,10 @@ test_expect_success $PREREQ "--validate respects absolute core.hooksPath path" '
test_expect_success $PREREQ "--validate hook supports header argument" '
test_when_finished "rm my-hooks.ran" &&
write_script my-hooks/sendemail-validate <<-\EOF &&
- filesize=$(stat -c%s "$2")
- if [ "$filesize" != "0" ]; then
- >my-hooks.ran
+ rm -f my-hooks.ran
+ if test -s "$2"
+ then
+ >my-hooks.ran
fi
exit 1
EOF
next prev parent reply other threads:[~2023-01-15 3:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-10 21:16 [PATCH v5 0/2] send-email: expose header information to git-send-email's sendemail-validate hook Strawbridge, Michael
2023-01-10 21:16 ` [PATCH v5 1/2] send-email: refactor header generation functions Strawbridge, Michael
2023-01-17 13:20 ` Ævar Arnfjörð Bjarmason
2023-01-17 15:13 ` Junio C Hamano
2023-01-17 21:36 ` Strawbridge, Michael
2023-01-10 21:16 ` [PATCH v5 2/2] send-email: expose header information to git-send-email's sendemail-validate hook Strawbridge, Michael
2023-01-14 1:17 ` Junio C Hamano
2023-01-14 16:03 ` Junio C Hamano
2023-01-14 16:06 ` Junio C Hamano
2023-01-15 3:34 ` Junio C Hamano [this message]
2023-01-17 4:09 ` Luben Tuikov
2023-01-17 4:29 ` Junio C Hamano
2023-01-17 4:56 ` Luben Tuikov
2023-01-17 13:23 ` Ævar Arnfjörð Bjarmason
2023-01-17 21:58 ` Strawbridge, Michael
2023-01-17 1:49 ` [PATCH v5 0/2] " Strawbridge, Michael
-- strict thread matches above, loose matches on Subject: below --
2023-01-17 1:37 Strawbridge, Michael
2023-01-17 1:37 ` [PATCH v5 2/2] " Strawbridge, Michael
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=xmqqfsccii86.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=Luben.Tuikov@amd.com \
--cc=Michael.Strawbridge@amd.com \
--cc=git@vger.kernel.org \
/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.