As detailed in patch3, after the fact / dynamic lore link generation continues to be awkward for managing work-in-progress patches across multiple versions. 'git notes' allows for workflow specific metadata that does not pollute upstream. The other desirable feature of notes is that they are displayed by default in cgit.
So the mainline history and upstream pull-requests remain clean, but work-in-progress series development can readily display which commits came from which messages. Example: $ b4 shazam -L [email protected] $ git show | grep -A1 Notes Notes: Link: https://patch.msgid.link/[email protected] Dan Williams (3): b4: Move linktrailer to a LoreMessage property b4, ty: Move git_get_rev_diff to __init__ for reuse in post processing shazam mbox: Add a --add-link-note option to shazam src/b4/__init__.py | 53 +++++++++++++++++++++++++----------------- src/b4/command.py | 2 ++ src/b4/mbox.py | 58 ++++++++++++++++++++++++++++++++++++++++++++++ src/b4/ty.py | 7 +----- 4 files changed, 93 insertions(+), 27 deletions(-) base-commit: f760a0468f91296750af072f7b3aed916f217e77 -- 2.51.0
