On Wed, 29 Nov 2006, Joseph Wakeling wrote: > > Linus Torvalds wrote: > > Now, with small changes, "git blame -C" will just ignore copies entirely, > > Obvious when I think about it, otherwise every 'int i;' in the kernel > would have a huge blame list ... :-O Indeed. We didn't do that heuristic originally, and the most common sequence that was "blamed" on being copied from somewhere else was something like the string "<tab><tab><tab>}<nl><tab><tab>}<nl><tab>}<nl>" which is obviously very common in C, especially when you have coding conventions and people follow them ;) > > them in the second commit (but if I instead create the second file in the > > second commit, and do the movement in the third commit, git blame -C works > > again ;). > > Actually my setup was like the latter situation you describe, so blame > was probably working fine and just ignoring the small change. But > serendipity is a wonderful thing. :-) Yeah. As it turns out, the bug was really that "git blame" ended up just not showing the filenames (that it had followed correctly), because it had decided (incorrectly) that they weren't interesting because it all came from the same commit, and it had already shown that commit (just not that _file_ in that commit). So it's fixed now, and probably would never trigger except for the stupid special case that was "let's just show an example of this" ;) Linus - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html