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

blame follows renames, but log doesn't

From
Martin Langhoff <martin.langhoff@gmail.com>
Date
Jun 19, 2007, 01:10 UTC
Message-ID
<46a038f90706181810p716f914al4d9abba5bfe7eb5@mail.gmail.com>
Hi all,

when I show git to newbies or demo it to people using other SCMs, and we get to the rename part of the conversation, I discuss and show how GIT's approach is significantly better than explicit recording of renames.

One great example is git-blame -- actually more spectacular with the recent git gui blame improvements. But git-log still doesn't do it.

If I say
   git blame git-cvsimport.perl  # goes to the true origin like a champ
   git log git-cvsimport.perl # stops at the Big Tool Rename

In thread in May Linus posted a PoC patch to get git-blame to do it http://marc.info/?l=git&m=117347893211567&w=2 , and outlined the reasons why it'd be wrong to try to do that in git-log -- but it didn't come to happen :-/

cg-log used to have some Perl logic that could do this -- it didn't always work, but I'm sometimes tempted to go back to it, and review it.

Linus said:
> But it's an example of the fact that yes, git can do this, but we're so
> stupid that we don't really accept it.

And I'm sure people can cope with git blame --log path/to/file and we can add a note to git-log manpage about renames being reported by blame instead.

And I kind of hate having to reply to things like these
    http://www.markshuttleworth.com/archives/125
cheers
martin
Next: Sam Vilain
Message 1 of 10 in “blame follows renames, but log doesn't”
  1. Martin LanghoffJun 19, 2007
  2. Sam VilainJun 19, 2007
  3. Theodore TsoJun 19, 2007
  4. Martin LanghoffJun 19, 2007
  5. Junio C HamanoJun 19, 2007
  6. Steven GrimmJun 19, 2007
  7. Directory renames (was Re: blame follows renames, but log doesn't)Steven Grimm, Jun 19, 2007
  8. Sam VilainJun 20, 2007
  9. Steven GrimmJun 20, 2007
  10. Jakub NarebskiJun 20, 2007

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.