Git development
 help / color / mirror / Atom feed
From: "Mark C. Chu-Carroll" <markchucarroll@fastmail.com>
To: git@vger.kernel.org
Cc: "Mark C. Chu-Carroll" <markchucarroll@fastmail.com>
Subject: [PATCH v5 0/3] t40*: modernize
Date: Tue, 22 Sep 2026 10:31:16 -0400	[thread overview]
Message-ID: <20260922143119.3313620-1-markchucarroll@fastmail.com> (raw)

Changes in v5:
- Update t4001.sh to the correct commit version. (Argh!)

- Link to v4: https://lore.kernel.org/git/20260918171847.2670739-1-markchucarroll@fastmail.com/

Changes in v4:
- use a "test_expect_success 'setup'" instead of setup functions
- make capitalization in test assertions consistent.
- improve naming of rename tests.
- make all indentations use tabs correctly.

- Link to v3: https://lore.kernel.org/all/20260917195436.1102981-1-markchucarroll@fastmail.com/

Changes in v3:
- Correct cover letter and commit message issues

- Link to v2: https://lore.kernel.org/all/20260910-modernize-t4001-v2-0-ac53e9f5d717@fastmail.com/

Changes in v2:
- Merged setups into main test bodies.
- Removed unnecessary echos.
- Cleaned up here-docs.
- Updated names to modern style.

- Link to v1: https://patch.msgid.link/20260908-modernize-t4001-v1-0-cab3933a173f@fastmail.com

Mark C. Chu-Carroll (3):
  t4001: modernize
  t4009: modernize
  t4010: modernize

 t/t4001-diff-rename.sh   |  91 +++++++++++--------------
 t/t4009-diff-rename-4.sh | 142 +++++++++++++++++++--------------------
 t/t4010-diff-pathspec.sh | 120 ++++++++++++++++-----------------
 3 files changed, 166 insertions(+), 187 deletions(-)

-- 
2.53.0


             reply	other threads:[~2026-09-22 14:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-22 14:31 Mark C. Chu-Carroll [this message]
2026-09-22 14:31 ` [PATCH v5 1/3] t4001: modernize Mark C. Chu-Carroll
2026-09-22 19:41   ` Junio C Hamano
2026-09-22 14:31 ` [PATCH v5 2/3] t4009: modernize Mark C. Chu-Carroll
2026-09-22 14:31 ` [PATCH v5 3/3] t4010: modernize Mark C. Chu-Carroll

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=20260922143119.3313620-1-markchucarroll@fastmail.com \
    --to=markchucarroll@fastmail.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