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

blame not working well?

From
Junio C Hamano <junkio@cox.net>
Date
Apr 6, 2006, 00:11 UTC
Message-ID
<7vacazy33w.fsf@assigned-by-dhcp.cox.net>

I was having fun updating blame.c to use the built-in xdiff instead of spawning and reading from external GNU diff (it is currently in "next" branch). It seems to pass the trivial testsuite case but I noticed for example annotating Makefile, sha1_name.c, or blame.c in git.git repository seems to show quite bogus annotation. One extreme case is the Makefile; for all but one line is blamed for the very initial commit made by Linus X-<. One good news for me is that the version before this change has the same breakage. One bad news is this seems to have been broken for some time.

Bisecting indicates 2a0925be3512451834ec9a3e023f4cff23c1cfb7 is the first bad commit, but I do not see how the change can break it. I'll continue digging it, but if you have a chance, could you take a look, too?

Next: Junio C Hamano
Message 1 of 2 in “blame not working well?”
  1. Junio C HamanoApr 6, 2006
  2. Junio C HamanoApr 6, 2006

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.