That's actually neigh impossible for a conflictless merge commit. gitArtur Malabarba <bruce.connor.am@gmail.com> writes:
> 2015-12-03 17:44 GMT+00:00 David Kastrup <dak@gnu.org>:
>> How would you check using git-blame that he did not accidentally revert
>> changes in a bad merge? Neither the old nor the new lines would be
>> traced to him.
>
> I had already checked (and stated) earlier that he didn't revert
> anything (with the diffs). Now I just checked whether he had "taken
> ownership" of any previous changes (with blame).
blame should not likely attribute anything to the committer of a merge
but manually resolved merge conflicts.
--
David Kastrup