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

Re: [PATCH] headers: Preserve 'change-id' header in rebase / cherry-pick.

From
NWNico Williams <nico@cryptonector.com>
Date
Apr 7, 2026, 05:02 UTC
Message-ID
<adSPznztKWo63Tjr@ubby>
In-Reply-To
<adSO6zPwtFOWBcOw@ubby>
On Mon, Apr 06, 2026 at 11:58:19PM -0500, Nico Williams wrote:
> Maybe that's the trick: local configuration for determining the
> copy-or-drop semantic for different operations, and maybe hooks for
> altering when copying.  [...]

I should add that I would want an original-change-id header that could be used (again, optionally) to relate commits that get cherry-picked or rebased but end up having different change-ids.

Previous: Nico WilliamsNext: Junio C Hamano
Message 4 of 12 in “headers: Preserve 'change-id' header in rebase / cherry-pick.”
  1. headers: Preserve 'change-id' header in rebase / cherry-pick.Matt Stark, Apr 7, 2026
  2. Junio C HamanoApr 7, 2026
  3. Nico WilliamsApr 7, 2026
  4. Nico WilliamsApr 7, 2026
  5. Junio C HamanoApr 7, 2026
  6. Phillip WoodApr 7, 2026
  7. Nico WilliamsApr 7, 2026
  8. Junio C HamanoApr 7, 2026
  9. Nico WilliamsApr 7, 2026
  10. Junio C HamanoApr 7, 2026
  11. Phillip WoodApr 7, 2026
  12. brian m. carlsonApr 7, 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.