The blame view supports going back to the previous commit:
after pressing b on some commit in blame mode (to show the blame view starting from that commit), we can use < to go back.

I suggest that we extend this feature to work across blame views, where it would be more useful to me.

When I use git blame to find the origin of a line, I oftend need to traverse commits that just moved the line.
I'll describe what I usually with the of how to find the origin of the first line in README.adoc.

1. Run tig blame 529182c -- README.adoc
2. Press <Enter> to inspect the commit that added the first line (c91ba8f).
   Observe that it's just a cosmetic change, which we want to skip over.
3. Run :272 to go to the place in the diff where first README-line was changed.
   Now we are on the deleted line -Tig: text-mode interface for git
4. Press b to go to the commit that introduced that line (b8ae934).
5. Proposed feature: now, pressing < (back) should take me back to the commit in the first blame-view. This doesn't happen because each view has a separate history.

I'm not sure how to implement this. I think there is already just one blame-view instance, so it should be enough to simply not delete the old blame-view history when creating a new one.