git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [RFC PATCH 0/2] Support --verbose in git history

From
Ben Knoble <ben.knoble@gmail.com>
Date
Nov 11, 2026, 15:39 UTC
Message-ID
<6F40E344-D1D1-487E-B5C4-1ADC0B06F749@gmail.com>
In-Reply-To
<avR1u_y2IQ8WoJXe@pks.im>
Show 56 quoted lines
> Le 11 nov. 2026 à 09:03, Patrick Steinhardt <ps@pks.im> a écrit :
> 
> On Wed, Nov 11, 2026 at 01:57:46PM +0000, Phillip Wood wrote:
>> Hi Patrick
>> 
>>> On 11/11/2026 10:46, Patrick Steinhardt wrote:
>>> On Tue, Nov 10, 2026 at 12:15:20PM -0500, Ben Knoble wrote:
>>>>> Le 10 nov. 2026 à 08:13, Karthik Nayak <karthik.188@gmail.com> a écrit :
>>>>> Phillip Wood <phillip.wood123@gmail.com> writes:
>>>>>> 
>>>>>> Another case where we might not want the diff is scripted editing as it
>>>>>> is much easier if the script does not have to worry about the diff
>>>>>> getting in the way of its edits. Personally I'd be happy to see this on
>>>>>> by default - the history command is marked as experimental so if having
>>>>>> it on by default rather than following "commit.verbose" proves to be
>>>>>> problematic we can always change it in the future. If we were staring
>>>>>> again I'd also make "commit.verbose" on by default as well so maybe I'm
>>>>>> biased.
>>>>>> 
>>>>> I'm on board with this suggestion. Plus, I see 'git history' to be more
>>>>> user facing and it's always nicer to have better defaults for users.
>>>>> Showing diffs and verbose information seems to be inline with that. We
>>>>> could add an option to disable such output for scripts (but that can be
>>>>> done later as you suggested).
>>>>> <signature.asc>
>>>> 
>>>> I can live with opt-out as long as I can turn it off via config.
>>> 
>>> Yeah, agreed. For me there's two important parts, where being able to
>>> disable this is the first one. The second part is that we need to make
>>> sure that such a format can work for every subcommand of git-history(1)
>>> so that we don't have to have multiple different formats for it.
>> 
>> Can I just check what you mean by "format" please. It is not clear if that
>> refers to the option name, or the way the diff is presented in the message
>> template (or both?).
> 
> Both probably, but what I meant is the output format. So it would need
> to be able to cover:
> 
>  - Changes to the commit layout (e.g. `git history split`).
> 
>  - Changes to the commit order (a future `git history move`).
> 
>  - Changes to the commit message.
> 
>  - Updates to multiple references.
> 
> I don't think we need to have everything implemented in a first
> iteration. But the output format should be flexible enough to display
> these kinds of changes.
> 
> To me it almost feels like what we want is essentially the format used
> by git-range-diff(1).
> 
> Patrick

Interesting; I certainly would appreciate range-diff-like content *somewhere* when using git-history. The original proposal was more like commit’s verbose diff in the editor, though, and I can see a desire to have that in all of the supported subcommands, too (maybe just as a reminder).

Decisions, decisions…
Previous: Patrick SteinhardtNext: Patrick Steinhardt
Message 15 of 19 in “Support --verbose in git history”
  1. 0/2 Support --verbose in git historyJelle van der Waa, Nov 7, 2026
  2. 1/2 history: drop redundant strbuf_stripspace()Jelle van der Waa, Nov 7, 2026
  3. 2/2 history: add --verbose option for rewordJelle van der Waa, Nov 7, 2026
  4. Phillip WoodNov 9, 2026
  5. D. Ben KnobleNov 7, 2026
  6. Phillip WoodNov 9, 2026
  7. Karthik NayakNov 9, 2026
  8. D. Ben KnobleNov 9, 2026
  9. Phillip WoodNov 9, 2026
  10. Karthik NayakNov 10, 2026
  11. Ben KnobleNov 10, 2026
  12. Patrick SteinhardtNov 11, 2026
  13. Phillip WoodNov 11, 2026
  14. Patrick SteinhardtNov 11, 2026
  15. Ben KnobleNov 11, 2026
  16. Patrick SteinhardtNov 11, 2026
  17. Jelle van der WaaNov 16, 2026
  18. Ben KnobleNov 17, 2026
  19. Junio C HamanoNov 17, 2026

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.