From: Jeff King <peff@peff.net>
To: Eric Sunshine <sunshine@sunshineco.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 1/2] t7422: replace confusing printf with echo
Date: Tue, 24 Jun 2025 06:05:20 -0400 [thread overview]
Message-ID: <20250624100520.GA636332@coredump.intra.peff.net> (raw)
In-Reply-To: <CAPig+cSLJ57+ZU1TreHajAqbQwBD7TRUt3bxRDTcHCjS88xmLg@mail.gmail.com>
On Mon, Jun 23, 2025 at 01:59:48PM -0400, Eric Sunshine wrote:
> > diff --git a/t/t7422-submodule-output.sh b/t/t7422-submodule-output.sh
> > @@ -180,7 +180,8 @@ test_expect_success !MINGW 'git submodule status --recursive propagates SIGPIPE'
> > - printf "[submodule \"sm-$i\"]\npath = recursive-submodule-path-$i\n" "$i" ||
> > + echo "[submodule \"sm-$i\"]" &&
> > + echo "path = recursive-submodule-path-$i" ||
>
> This looks obviously correct and, as the commit message says, is
> almost certainly easier to read, but I was more than a little
> surprised to see the patch since I thought this code had been fixed
> previously[*] and had some discussion around it.
>
> [*] https://lore.kernel.org/git/20250403144852.19153-1-sn03.general@gmail.com/
Ah, interesting, I hadn't seen that one. I am happy with either
solution, but IMHO what I posted with "echo" is a bit more readable.
-Peff
next prev parent reply other threads:[~2025-06-24 10:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-23 10:55 [PATCH 0/2] test_seq format option Jeff King
2025-06-23 10:55 ` [PATCH 1/2] t7422: replace confusing printf with echo Jeff King
2025-06-23 17:59 ` Eric Sunshine
2025-06-24 10:05 ` Jeff King [this message]
2025-06-23 10:56 ` [PATCH 2/2] test-lib: teach test_seq the -f option Jeff King
2025-06-23 16:10 ` Junio C Hamano
2025-06-23 16:25 ` Justin Tobler
2025-06-24 10:11 ` [PATCH 3/2] test-lib: document test_seq's "-f" option Jeff King
2025-06-25 0:02 ` Justin Tobler
2025-06-23 17:27 ` [PATCH 2/2] test-lib: teach test_seq the -f option Todd Zullinger
2025-06-24 10:16 ` Jeff King
2025-06-24 13:42 ` Todd Zullinger
2025-06-24 6:22 ` Eric Sunshine
2025-06-24 10:36 ` Jeff King
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=20250624100520.GA636332@coredump.intra.peff.net \
--to=peff@peff.net \
--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