From: Solly <solobarine@gmail.com>
To: git@vger.kernel.org
Cc: Solly <solobarine@gmail.com>
Subject: [PATCH v2 0/1] *** t2401: update path checks using test_path helpers ***
Date: Wed, 15 Oct 2025 15:03:28 +0100 [thread overview]
Message-ID: <20251015140329.13691-1-solobarine@gmail.com> (raw)
In-Reply-To: <20251014161446.6135-1-solobarine@gmail.com>
***
Thank you for the timely review.
I applied the corrections and resolved the issues highlighted
in the initial patch and used the appropriate test_helpers.
***
Solly (1):
t2401: update path checks using test_path helpers
t/t2401-worktree-prune.sh | 34 +++++++++++++++++-----------------
1 file changed, 17 insertions(+), 17 deletions(-)
base-commit: 60f3f52f17cceefa5299709b189ce6fe2d181e7b
--
2.34.1
next prev parent reply other threads:[~2025-10-15 14:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-14 16:14 [PATCH 1/1] t: update path checks using test_path helpers Solly
2025-10-14 18:19 ` Junio C Hamano
2025-10-14 18:27 ` Usman Akinyemi
2025-10-14 18:47 ` Eric Sunshine
2025-10-15 14:03 ` Solly [this message]
2025-10-15 14:03 ` [PATCH v2 1/1] t2401: " Solly
2025-10-15 20:38 ` 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=20251015140329.13691-1-solobarine@gmail.com \
--to=solobarine@gmail.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 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).