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

Re: forcing an in-body From header

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 26, 2022, 17:11 UTC
Message-ID
<xmqqtu5zx74e.fsf@gitster.g>
In-Reply-To
<c403e526-7455-4f26-fcef-97c99f9af539@rasmusvillemoes.dk>
Rasmus Villemoes <rv@rasmusvillemoes.dk> writes:
> I looked into the code, and while this is obviously just a hacky patch
> to see that I found the right spot, it doesn't seem to be too hard to
> implement properly.

I agree with you on all points in the above sentence ;-) I do not think anybody minds if a command line option to "git format-patch" added in builtin/log.c::cmd_format_patch() and a new configuration variable taught to builtin/log.c::git_format_config() that gives the default value for the new "force_in_body_from" member that will be added to "struct rev_info" and relayed to "pretty_print_context" when log-tree.c::fmt_output_commit() calls format_commit_messages().

Or something like that.
Previous: Rasmus Villemoes
Message 5 of 5 in “forcing an in-body From header”
  1. Rasmus VillemoesAug 26, 2022
  2. Konstantin RyabitsevAug 26, 2022
  3. Junio C HamanoAug 26, 2022
  4. Rasmus VillemoesAug 29, 2022
  5. Junio C HamanoAug 26, 2022

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.