git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: log -m output

From
SKSemyon Kirnosenko <kirnosenko@mail.ru>
Date
Oct 7, 2019, 17:00 UTC
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:
Show 26 quoted lines
> 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

-- 
С Уважением,
Кирносенко С.И.
Previous: SZEDER GáborNext: Elijah Newren
Message 3 of 5 in “log -m output”
  1. Semyon KirnosenkoOct 7, 2019
  2. SZEDER GáborOct 7, 2019
  3. Semyon KirnosenkoOct 7, 2019
  4. Elijah NewrenOct 7, 2019
  5. Semyon KirnosenkoOct 7, 2019

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.