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

Git log follow question

From
AKAlbert Krawczyk <albert@burgmann.anu.edu.au>
Date
May 14, 2010, 00:57 UTC
Message-ID
<006d01caf300$703e96a0$50bbc3e0$@burgmann.anu.edu.au>
Hi Everybody,

I'm having an issue understanding the way git log --follow works with git log --parents

When I run git log --parents --pretty=format:Commit:%H%nParent:%P%n%n alloc.c I get: Commit:4b25d091ba53c758fae0096b8c0662371857b9d9 Parent:100c5f3b0b27ec6617de1a785c4ff481e92636c1

Commit:100c5f3b0b27ec6617de1a785c4ff481e92636c1 Parent:2c1cbec1e2f0bd7b15fe5e921d287babfd91c7d3

Commit:2c1cbec1e2f0bd7b15fe5e921d287babfd91c7d3 Parent:579d1fbfaf25550254014fa472faac95f88eb779

Commit:579d1fbfaf25550254014fa472faac95f88eb779 Parent:855419f764a65e92f1d5dd1b3d50ee987db1d9de

Commit:855419f764a65e92f1d5dd1b3d50ee987db1d9de Parent:

When I try to run git log --parents --follow I get this: git log --parents --follow --pretty=format:Commit:%H%nParent:%P%n%n alloc.c

Commit:4b25d091ba53c758fae0096b8c0662371857b9d9 Parent:75b44066f3ed7cde238cdea1f0bf9e2f1744c820

Commit:100c5f3b0b27ec6617de1a785c4ff481e92636c1 Parent:2c1cbec1e2f0bd7b15fe5e921d287babfd91c7d3

Commit:2c1cbec1e2f0bd7b15fe5e921d287babfd91c7d3 Parent:f948792990f82a35bf0c98510e7511ef8acb9cd3

Commit:579d1fbfaf25550254014fa472faac95f88eb779 Parent:446c6faec69f7ac521b8b9fc2b1874731729032f

Commit:855419f764a65e92f1d5dd1b3d50ee987db1d9de Parent:64e86c57867593ba0ee77a7b0ff0eb8e9d4d8ed5

As you can see git log --parents and git log --follow --parents produce very different results, and as far as I can tell they should produce identical outputs.

Could somebody tell me if I'm doing something wrong with the syntax? Or have I stumbled onto a quirk I fail to understand?

Thanks, Albert

Next: Bo Yang
Message 1 of 12 in “Git log follow question”
  1. Albert KrawczykMay 14, 2010
  2. Bo YangMay 14, 2010
  3. Jeff KingMay 14, 2010
  4. Linus TorvaldsMay 14, 2010
  5. Martin LanghoffMay 14, 2010
  6. Linus TorvaldsMay 14, 2010
  7. Jeff KingMay 25, 2010
  8. Linus TorvaldsMay 25, 2010
  9. Jeff KingMay 26, 2010
  10. Linus TorvaldsMay 26, 2010
  11. Albert KrawczykMay 14, 2010
  12. Albert KrawczykMay 14, 2010

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.