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

Re: [PATCH] [RFC] rebase -m: partial support for copying extra commit headers

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 9, 2025, 15:36 UTC
Message-ID
<xmqq34ehtki8.fsf@gitster.g>
In-Reply-To
<7f744f34-050c-4d8b-b5fc-aae622c3c5b6@gmail.com>
Phillip Wood <phillip.wood123@gmail.com> writes:
> That's true and we could have a config key to select which "extra"
> headers are propagated.
No, please don't.  No such config key should ever exist.

If something has a defined semantics, which all projects that use Git can agree on, that is solid enough to deserve to be in the header part of the commit object (as opposed to one of the trailers with user-defined semantics that can vary from project to project), there should never be a way to give it different semantics by tweaking whether it is or it is not propagated when rewriting.

Previous: Phillip Wood
Message 6 of 6 in “[RFC] rebase -m: partial support for copying extra commit headers”
  1. [RFC] rebase -m: partial support for copying extra commit headersPhillip Wood via GitGitGadget, Apr 7, 2025
  2. brian m. carlsonApr 8, 2025
  3. Phillip WoodApr 8, 2025
  4. Junio C HamanoApr 8, 2025
  5. Phillip WoodApr 9, 2025
  6. Junio C HamanoApr 9, 2025

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.