From: Junio C Hamano <gitster@pobox.com>
Date: Wed, 06 Dec 2017 17:22:21 GMT
Subject: Re: git blame --reverse doesn't find line in HEAD
Message-ID: <xmqqh8t3hiuq.fsf@gitster.mtv.corp.google.com>
In-Reply-To: <CA+SQVf24rcQ1iKAQBW0Ky7Qm8zuF3Esw8qMKvG+KCbCA-mCcfA@mail.gmail.com>

Nick Snyder <nick@sourcegraph.com> 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.