From: Semyon Kirnosenko <kirnosenko@mail.ru>
Date: Mon, 07 Oct 2019 17:00:20 GMT
Subject: Re: log -m output
Message-ID: <7b9c0b0b-2a1c-d4d3-13ba-f020ff15d5ad@mail.ru>
In-Reply-To: <20191007164310.GA11529@szeder.dev>

On 2019-10-07 20:43, SZEDER Gábor wrote:
> On Mon, Oct 07, 2019 at 07:14:25PM +0400, Semyon Kirnosenko wrote:
>> I have a question about log command.
>> Probably I'm just missing something but anyway.
>> I can illustrate the question on the repository of Git.
>> Let's look at revision 1ed91937
>> It is a merge based on pair of revisions a9572072 and 294c695d.
>> According to blame these parent revisions have different content for
>> delta.h file.
> 
> I'm not sure what you mean by this statement; what blame command did
> you run?
> 
>> But when I get log with -m flag for merge revision, I can't see that
>> file in the list of changed files.
>> Why?
> 
> The contents of 'delta.h' is identical in both parents of that merge:
> 
>    $ git diff a9572072 294c695d delta.h
>    $
>    # no difference
> 
> So 'git log -m' does the right thing by not showing 'delta.h'.
> 
> .
> 

But blame shows different results:

git blame a9572072 delta.h
git blame 294c695d delta.h

-- 
С Уважением,
Кирносенко С.И.