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
EHEwout ter Hoeven <ewoutterhoeven@live.nl>
Date
Nov 15, 2026, 11:03 UTC
Message-ID
<GV4P192MB328727D81CAED2956E2C682BC07D2@GV4P192MB3287.EURP192.PROD.OUTLOOK.COM>
In-Reply-To
<adWTKt20ISC3qz2g@fruit.crustytoothpaste.net>
On 2026-04-07 at 23:28, brian m. carlson wrote:
> Absent some well-defined documentation describing what it means, I don't
> see how it could provide good value.
A concrete use case could be stacked pull/merge requests.

GitHub's stacked PRs (CLI in github/gh-stack) and GitLab's experimental "glab stack" both have to answer "is this rewritten commit the same change as before?" after every rebase. Without an identity that survives rewrites they guess from branch names, recorded bases and patch IDs, and the guesses fail in practice:

 - Renaming a branch with plain "git branch -m" strands the stack,
   because the tool tracks layers by branch name
   (https://github.com/github/gh-stack/issues/423).
 - When a lower layer is rewritten, its old commits are replayed onto
   the new copies because patch IDs no longer match; one user reports
   61 commits replayed, 53 of them already in the parent
   (https://github.com/github/gh-stack/discussions/600).
 - In a review of glab's stacked diffs, GitLab's Git (Gitaly) engineers
   discussed moving towards change IDs for the same reason
   (https://gitlab.com/gitlab-org/cli/-/issues/8040).

Each tool works around this with its own metadata, which plain git commands then invalidate. A header that git preserves would let them use git as the source of truth.

Previous: brian m. carlsonNext: brian m. carlson
Message 13 of 14 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
  13. Ewout ter HoevenNov 15, 2026
  14. brian m. carlsonNov 15, 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.