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

git log --follow after subtree merge

From
JGJonny Gilchrist <jonnygilchrist@gmail.com>
Date
May 10, 2017, 14:46 UTC
Message-ID
<CA+qhfwO4=1X9fNCW2PeKSgqUHV-z26qhvr_yXfz1QGApJ_roRQ@mail.gmail.com>
Hi,

After doing a subtree merge, using 'git log' and 'git log --follow' on files in the subtree show only the merge commit in which they were added.

After reading around I understand that the issue is that git log --follow doesn't track renames that occur during a merge.

Has there been any work (or are there any plans) to allow git log --follow to work in this case? I couldn't find anything in the mailing list archives aside from a couple of threads from 2011 explaining the issue.

Thanks, J.

Next: Samuel Lijin
Message 1 of 5 in “git log --follow after subtree merge”
  1. Jonny GilchristMay 10, 2017
  2. Samuel LijinMay 10, 2017
  3. Jeff KingMay 11, 2017
  4. Jeff KingMay 11, 2017
  5. Konstantin KhomoutovMay 11, 2017

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.