Nick Snyder <nick@xxxxxxxxxxxxxxx> writes: > This can be reproduced on Linux and Mac. This behavior seems to be a bug. Can you bisect to see when the feature stopped working as you expect? Unlike a forward blame, where the command tries to find a commit that is responsible for a line being in the final result (i.e. typically, HEAD), a reverse blame is not about finding a commit that is responsible for a line (that used to be in the oldest commit) not being in a more recent codebase. It finds up to which commit each line survived without getting touched since the oldest commit in the range.
