From: Lucas Seiki Oshiro <lucasseikioshiro@gmail.com>
To: Mansi Singh via GitGitGadget <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, Mansi Singh <mansimaanu8627@gmail.com>
Subject: Re: [PATCH] t7605: use test_path_is_file instead of test -f
Date: Wed, 25 Feb 2026 16:04:59 -0300 [thread overview]
Message-ID: <2C345ED6-BE80-4947-A1B9-4065CB54086C@gmail.com> (raw)
In-Reply-To: <pull.2050.git.1771911268805.gitgitgadget@gmail.com>
Hi, Mansi!
> Replace old-style 'test -f' path checks with the modern
> test_path_is_file helper in the merge_c1_to_c2_cmds block.
>
> The helper provides clearer failure messages and is the
> established convention in Git's test suite.
>
> These instances were found using:
> grep -rn "test -[efd]" t/ --include="*.sh"
I don't think this information is relevant to be placed in
the commit description. Perhaps it would better placed after
the scissors mark (the --- after the message) which is sent
to the mailing list but ignored in the final commit.
Btw, since we're in Git we can use Git's special powers to
do that. This is equivalent to your command line:
$ git grep 'test -[efd]' -- 't/*.sh'
And this may be more useful, separating the output per file
and using pathspecs to filter the tests (files that begin with
"t") from other helper scripts inside t/:
$ git grep --heading --break 'test -[efd]' -- 't/t*.sh'
I wrote a blog post about git-grep and other tools [1] that
may be useful for you.
> - test -f c0.c &&
> - test -f c1.c &&
> - test -f c2.c &&
> + test_path_is_file c0.c &&
> + test_path_is_file c1.c &&
> + test_path_is_file c2.c &&
The code itself looks good to me!
[1] https://lucasoshiro.github.io/posts-en/2023-02-13-git-debug/#git-grep
next prev parent reply other threads:[~2026-02-25 19:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-24 5:34 [PATCH] t7605: use test_path_is_file instead of test -f Mansi Singh via GitGitGadget
2026-02-25 19:04 ` Lucas Seiki Oshiro [this message]
2026-02-26 0:57 ` [PATCH v2] " Mansi Singh via GitGitGadget
-- strict thread matches above, loose matches on Subject: below --
2026-03-10 5:33 [PATCH] " Mansi Singh via GitGitGadget
2026-03-10 13:30 ` Junio C Hamano
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=2C345ED6-BE80-4947-A1B9-4065CB54086C@gmail.com \
--to=lucasseikioshiro@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=mansimaanu8627@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