From: matthieu@talbot.audio
To: git@vger.kernel.org
Subject: malformed commit messages for git version 2.42.0 when "commit.verbose true"
Date: Mon, 23 Oct 2023 10:36:56 +0000 [thread overview]
Message-ID: <9a72287d979a0bd9dce390478d8522139646fb4e@talbot.audio> (raw)
Hello,
I recently set the option `commit.verbose` to `true` for git version 2.42.0, and I really like it.
However, most of the time, commits are malformed if I don’t remove the diff after the marker
`# ------------------------ >8 ------------------------`
I would expect that anything after the marker is automatically removed by git, or could it be that some pre-commit script see the raw commit message before it is cleaned-up by git itself?
Best,
Matthieu
reply other threads:[~2023-10-23 10:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=9a72287d979a0bd9dce390478d8522139646fb4e@talbot.audio \
--to=matthieu@talbot.audio \
--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;
as well as URLs for NNTP newsgroup(s).