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

git-replay/git-history lose notes

From
D. Ben Knoble <ben.knoble@gmail.com>
Date
Aug 4, 2026, 20:06 UTC
Message-ID
<CALnO6CAN1=dgRsYjABfa3CJkGnvb139EcrzS9EnX43i3szOgtQ@mail.gmail.com>
Hi all,

I don't think this has been reported or discussed yet, though my apologies if my search skills just didn't find it.

It looks like git-replay and git-history will drop notes (or rather, not carry them over) when rewriting history. I've seen this both with "git replay --onto=… …" and "git history fixup" recently, though I suspect it affects all the modes.

Fortunately when I check range-diffs before pushing out new versions, I notice notes have disappeared and can "git notes copy @{1}" or similar for a note at the tip. Recovery for the intermediate commits is a little more… involved… as I'm sure you can imagine.

Are notes out of scope for replay and history, or is this just a "nobody's gotten around to it yet"?

-- 
D. Ben Knoble
Next: Patrick Steinhardt
Message 1 of 9 in “git-replay/git-history lose notes”
  1. D. Ben KnobleAug 4, 2026
  2. Patrick SteinhardtAug 5, 2026
  3. D. Ben KnobleAug 5, 2026
  4. Phillip WoodAug 5, 2026
  5. D. Ben KnobleAug 5, 2026
  6. Junio C HamanoAug 5, 2026
  7. Elijah NewrenAug 7, 2026
  8. erik88Aug 7, 2026
  9. Elijah NewrenAug 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.