From: Jeff King <peff@peff.net>
To: git@vger.kernel.org
Subject: [PATCH 0/2] test_seq format option
Date: Mon, 23 Jun 2025 06:55:16 -0400 [thread overview]
Message-ID: <20250623105516.GA654296@coredump.intra.peff.net> (raw)
This is a small quality of life improvement for our test suite, stemming
from this discussion:
https://lore.kernel.org/git/20240408172638.GB1629595@coredump.intra.peff.net/
But somehow it took me over a year to get back to it. :-/
The first patch is a small cleanup in nearby code; the second one is the
interesting part.
[1/2]: t7422: replace confusing printf with echo
[2/2]: test-lib: teach test_seq the -f option
t/t0021-conversion.sh | 4 ++--
t/t0610-reftable-basics.sh | 6 +-----
t/t0612-reftable-jgit-compatibility.sh | 13 +++++--------
t/t0613-reftable-write-options.sh | 24 ++++--------------------
t/t1400-update-ref.sh | 10 ++--------
t/t5004-archive-corner-cases.sh | 5 +----
t/t6422-merge-rename-corner-cases.sh | 10 ++--------
t/t7422-submodule-output.sh | 9 +++------
t/test-lib-functions.sh | 9 ++++++++-
9 files changed, 28 insertions(+), 62 deletions(-)
-Peff
next reply other threads:[~2025-06-23 10:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-23 10:55 Jeff King [this message]
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
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=20250623105516.GA654296@coredump.intra.peff.net \
--to=peff@peff.net \
--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