Harald Nordgren's series follows an earlier mailing-list discussion. It targets the problem that 'git reflog' lists every step of a rebase and every branch switch, which makes it hard to see what was done and on which branch.

'--operations' shows one entry per command. A rebase is folded into the single entry that finished or aborted it, and entries that change no branch are left out. That covers branch switches and the "reset: moving to HEAD" that 'git stash' and 'git merge --abort' leave behind. '--historical-branch' decorates each entry with the branch HEAD was on when it was recorded, instead of the refs that currently point at the commit. The commit message notes that ordinary decorations don't help here because a rebased or amended commit has none.

Kristoffer Haugsbakk said it sounds very useful. He described the obscuring of reset points after a rebase as a classic problem, and said he sometimes uses ORIG_HEAD or makes a backup ref instead. Nordgren said he often picks commits one by one and runs 'git show' to find the right one.

Haugsbakk also criticized the first patch, which names the strings marking switches, renames and rebase steps. He said the message enumerates things without saying why, and that the reason, using these strings in more than one place without duplication, should come first. He also found some phrasing too passive to follow.

The two also discussed tig, which Haugsbakk showed can browse the reflog. Nordgren noted that Git options are passed through to tig, so 'tig reflog --operations' should work with the new option.