From: Junio C Hamano <gitster@pobox.com>
To: "Mark C. Chu-Carroll via B4 Relay"
<devnull+markchucarroll.fastmail.com@kernel.org>
Cc: git@vger.kernel.org,
"Mark C. Chu-Carroll" <markchucarroll@fastmail.com>
Subject: Re: [PATCH v2 1/3] Update t4001 to use modern syntax.
Date: Thu, 10 Sep 2026 10:56:22 -0700 [thread overview]
Message-ID: <xmqqv78ddm7t.fsf@gitster.g> (raw)
In-Reply-To: <20260910-modernize-t4001-v2-1-ac53e9f5d717@fastmail.com> (Mark C. Chu-Carroll via's message of "Thu, 10 Sep 2026 13:07:33 -0400")
"Mark C. Chu-Carroll via B4 Relay"
<devnull+markchucarroll.fastmail.com@kernel.org> writes:
> Subject: [PATCH v2 1/3] Update t4001 to use modern syntax.
Documentation/SubmittingPatches::[[summary-section]]
Also "git log --oneline --no-merges -60 origin -- t/" may give us
some hint.
> From: "Mark C. Chu-Carroll" <markchucarroll@fastmail.com>
>
Documentation/SubmittingPatches::[[describe-changes]]
> ---
Documentation/SubmittingPatches::[[sign-off]]
next prev parent reply other threads:[~2026-09-10 17:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-08 19:44 [PATCH 0/3] Update t40* tests to use modern style Mark C. Chu-Carroll via B4 Relay
2026-09-08 19:44 ` [PATCH 1/3] Update t4001 to use modern syntax Mark C. Chu-Carroll via B4 Relay
2026-09-08 20:48 ` Junio C Hamano
2026-09-08 19:44 ` [PATCH 2/3] Update t4009 to use modern style Mark C. Chu-Carroll via B4 Relay
2026-09-08 19:44 ` [PATCH 3/3] Update t4010 " Mark C. Chu-Carroll via B4 Relay
2026-09-10 17:07 ` [PATCH v2 0/3] Update t40* tests " Mark C. Chu-Carroll via B4 Relay
2026-09-10 17:07 ` [PATCH v2 1/3] Update t4001 to use modern syntax Mark C. Chu-Carroll via B4 Relay
2026-09-10 17:56 ` Junio C Hamano [this message]
2026-09-10 17:07 ` [PATCH v2 2/3] Update t4009 to use modern style Mark C. Chu-Carroll via B4 Relay
2026-09-10 17:07 ` [PATCH v2 3/3] Update t4010 " Mark C. Chu-Carroll via B4 Relay
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=xmqqv78ddm7t.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=devnull+markchucarroll.fastmail.com@kernel.org \
--cc=git@vger.kernel.org \
--cc=markchucarroll@fastmail.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