From: Subhaditya Nath <sn03.general@gmail.com>
To: gitster@pobox.com
Cc: git@vger.kernel.org, ps@pks.im, sn03.general@gmail.com,
sunshine@sunshineco.com
Subject: [PATCH] t7422: fix extra printf argument, eliminate loops
Date: Thu, 10 Apr 2025 00:41:10 +0530 [thread overview]
Message-ID: <20250409191139.29644-1-sn03.general@gmail.com> (raw)
In-Reply-To: <xmqqr021qkeh.fsf@gitster.g>
On Wed Apr 9, 2025 at 11:36 PM IST, Junio C Hamano wrote:
> The other one in the example in this thread could lose the for loop
> by doing
>
> printf "160000 commit $COMMIT\trecursive-submodule-path-%d\n" \
> $(test_seq 2000)
>
> but for uniformity with other parts that cannot lose "for" loop, I
> would not recommend going in that direction.
Interesting. I didn't know printf could be used like so.
The patch I sent earlier can also be re-written to lose the loop by
simply passing the output of test_seq via 'sed p' to print each number
twice!
next prev parent reply other threads:[~2025-04-09 19:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-03 14:48 [PATCH] t7422: remove extraneous argument to printf Subhaditya Nath
2025-04-03 17:05 ` Eric Sunshine
2025-04-09 16:19 ` Junio C Hamano
2025-04-09 16:29 ` Subhaditya Nath
2025-04-09 16:32 ` Subhaditya Nath
2025-04-09 17:00 ` Eric Sunshine
2025-04-09 18:06 ` Junio C Hamano
2025-04-09 19:11 ` Subhaditya Nath [this message]
2025-04-09 19:11 ` [PATCH] t7422: fix extra printf argument, eliminate loops Subhaditya Nath
2025-04-10 12:39 ` 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=20250409191139.29644-1-sn03.general@gmail.com \
--to=sn03.general@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=ps@pks.im \
--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).