# RFC adds `--verbose` to `git history reword`; Ben Knoble asks whether the name fits

_Showing the diff in the editor would match `git commit --amend --verbose`, but a reviewer wonders if "verbose" should mean something else in git-history._

Section: Patches. Edition of 2026-11-08. 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 sent an RFC to teach `git history reword` a `--verbose` option, so that the full diff appears when editing the commit message, as with `git commit --amend --verbose`. His implementation does not follow the commit.verbose configuration setting. He said he would like to land support for `reword` first, ideally with commit.verbose, and add other subcommands later.

He noted that split, squash and fixup could support the option under some conditions. For fixup that would mean without `--no-edit` or only with `--reedit-message`. A second patch removes a redundant strbuf_stripspace() call, since cleanup_message() with COMMIT_MSG_CLEANUP_ALL already does it.

D. Ben Knoble replied with a first thought on naming. Consistency with other commands is good, he said, but "verbose" might be better reserved for another meaning in git-history. He said he has sometimes wished the command would show the rewritten commits after running, in a form like "commit abc => def".

Because "verbose" can mean many things, he suggested something like `--commit-verbose`, `--diff-in-editor` or another name that makes the purpose clear. The thread had four messages and no other comments in the excerpts.
