Re: [PATCH 0/3] reflog: add --operations and --historical-branch
- From
- Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>
- Date
- Oct 15, 2026, 15:35 UTC
- Message-ID
- <f06c7de7-f9d5-4c7b-8c65-fc2cec1ee698@app.fastmail.com>
- In-Reply-To
- <CAHwyqnWyYhRZ0=byi3_yqT2phmVa2DY8XtxA8bQT=pwcetkMAg@mail.gmail.com>
On Thu, Oct 15, 2026, at 17:24, Harald Nordgren wrote:
Show 10 quoted lines
>> This sounds very useful. That you rebase many commits and then the reset >> points (where each one started and ended) get obscured in the reflog is >> classic for me. And I think many have had the same issue. This is why I >> sometimes use `ORIG_HEAD` instead, or maybe make a backup ref. > > Yes! I love the reflog. But I'm also endlessly confused by it. > > Sometimes I'll just pick all the commits one by one and do 'git show' > on them to figure out which one to actually pick. Not a great > experience.
:)
I got a bit curious about this forced workflow now. I tried the first terminal navigate-and-click Git tool I could think of, tig(1), and it turns out that you can do this:
$ tig reflog
$ # navigate up/down j/k
$ # See the commit message and diff with `d`