Re: What's cooking in git.git (Feb 2026, #04)
- From
- Phillip Wood <phillip.wood123@gmail.com>
- Date
- Feb 13, 2026, 16:06 UTC
- Message-ID
- <44b29844-1d3b-47cc-8a82-3ae167661f59@gmail.com>
- In-Reply-To
- <xmqq3435rk70.fsf@gitster.g>
On 12/02/2026 16:38, Junio C Hamano wrote:
Show 25 quoted lines
> 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.
Good point - I'd forgotten that the subject ends up in an email header. I've sent v2 as <cover.1770993281.git.phillip.wood@dunelm.org.uk>
Thanks
Phillip
> Thanks.