Johannes Schindelin <Johannes.Schindelin@xxxxxx> writes: > Speaking of GitGitGadget: I just encoutered a problem with your > `refs/notes/amlog` and I hope you can help me with that. > ... > When I ask `git notes --ref=refs/notes/gitster-amlog show > 4cec3986f017d84c8d6a2c4233d2eba4a3ffa60d` (the SHA-1 is the one > corresponding to `Message-Id: <...>` for that mail), it insists on > outputting > > 5902152ab02291af4454f24a8ccaf2adddefc306 It is not uncommon for me to have to do "am" the same patch twice when attempting to find the right branch/commit to base a change on, so the reverse direction that abuses the notes mechanism to map message id to resulting commits would be unreliable, especially given that they may need to further go through "rebase -i" or manual "cherry-pick <range>" depending on the situation. I am kind of surprised that the message-to-commit mapping still records any data that is remotely useful (these days, I only use it to run "show --notes=amlog" for commit-to-message mapping). I do not think I have anything special when amending the commit, but amlog notes should be updated in both diretions for its entries to stay correct across amending, I would think.
