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

Strange behaviour of git log --follow

From
VVictor <__vic@ngs.ru>
Date
Mar 7, 2019, 08:34 UTC
Message-ID
<web-53867248@mx30.intranet.ru>
Hello.
$ git log include/__vic/mutex.h
commit 9429293f8f8fb0819c77cf1f723567f6edc8fb6a
Merge: 96dd9a2 f484f4e
Author: __vic <__vic@ngs.ru>
Date:   2017-12-13 10:41:32 +0300
     Merge branch 'generic' into posix
commit f484f4e8aae32041ba56bdce12d1efd8491e94d5
Merge: 86b848a b9bbbe6
Author: __vic <__vic@ngs.ru>
Date:   2017-12-12 17:35:10 +0300
     waitable_event, thread, mutex
$ git log --follow include/__vic/mutex.h
$

Why --follow makes git produce truncated history for file that wasn't renamed?

My repository is available here https://github.com/2underscores-vic/__vic

Message 1 of 1 in “Strange behaviour of git log --follow”
  1. VictorMar 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.