# git history will make verbose commit-message editing the default, following commit.verbose

_After list feedback, Jelle van der Waa will drop the proposed --verbose option for `git history reword` and instead show the diff by default, with an opt-out._

Section: Discussion. Edition of 2026-11-17. Written by an AI editor from the thread "[RFC PATCH 0/2] Support --verbose in git history" (19 messages): https://gitlist.dev/t/66803

Jelle van der Waa posted an RFC adding --verbose to `git history reword`, so that editing a commit message shows the full diff the way `git commit --amend --verbose` does. He left out support for the commit.verbose configuration option. He noted that split, squash and fixup could also support it in some circumstances, and said he would like to land reword first, ideally with commit.verbose support.

In the review, Ben Knoble argued that even with a config setting, a command-line option is still wanted for deterministic behavior in interactive use or scripts. Junio C Hamano agreed and asked whether the opposite of --verbose should be --quiet, or whether OPT__VERBOSITY() should be used.

Van der Waa read most of the replies as agreeing that verbose should be the default, with a way to opt out. He said he will send a new patch that drops the --verbose option and makes verbose follow commit.verbose, on by default for git history. In his view, split, reword and fixup would turn it on, while drop has no way to interact with a commit message.

The new version has not yet been posted. Whether the opt-out is simply the existing commit.verbose setting or also a command-line flag is not settled in the excerpts.
