From: Junio C Hamano <gitster@pobox.com>
To: Phillip Wood <phillip.wood123@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Feb 2026, #04)
Date: Thu, 12 Feb 2026 08:38:27 -0800 [thread overview]
Message-ID: <xmqq3435rk70.fsf@gitster.g> (raw)
In-Reply-To: <53696dd3-1920-4777-a62e-bf7818bd228c@gmail.com> (Phillip Wood's message of "Thu, 12 Feb 2026 15:56:52 +0000")
Phillip Wood <phillip.wood123@gmail.com> writes:
> On 10/02/2026 22:21, Junio C Hamano wrote:
>>
>> * pw/commit-msg-sample-hook (2026-02-07) 3 commits
>> - templates: detect messages that contain a separator line
>> - templates: detect commit messages containing diffs
>> - templates: add .gitattributes entry for sample hooks
>>
>> Update sample commit-msg hook to complain when a log message has
>> material mailinfo considers the end of log message in the middle.
>>
>> Will merge to 'next'?
>> source: <cover.1770476279.git.phillip.wood@dunelm.org.uk>
>
> I'm planning a re-roll to handle subject lines that start with "diff -"
> after using this hook while preparing
> <2a8cc2d6c37f25a58823b501500165d597321749.1770911599.git.phillip.wood@dunelm.org.uk>.
> Such subject lines are safe because "git format-patch" prefixes them
> with [PATCH]. I think I'll probably drop the last patch as well.
OK. Even though the "[PATCH] " prefix is optional in format-patch
output, it will be on the line that begins with "Subject:", so it
should be safe, so you can safely exclude the lines in the first
paragraph of a commit message from the check.
Thanks.
next prev parent reply other threads:[~2026-02-12 16:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-10 22:21 What's cooking in git.git (Feb 2026, #04) Junio C Hamano
2026-02-11 14:23 ` ps/object-info-bits-cleanup (was: What's cooking in git.git (Feb 2026, #04)) Patrick Steinhardt
2026-02-11 17:35 ` ps/object-info-bits-cleanup Junio C Hamano
2026-02-12 6:34 ` ps/object-info-bits-cleanup Patrick Steinhardt
2026-02-11 20:46 ` What's cooking in git.git (Feb 2026, #04) Junio C Hamano
2026-02-12 10:26 ` Samuel Abraham
2026-02-12 15:56 ` Phillip Wood
2026-02-12 16:38 ` Junio C Hamano [this message]
2026-02-13 16:06 ` Phillip Wood
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=xmqq3435rk70.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=phillip.wood123@gmail.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