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
> I think Junio screwed up at some point. I'll send him a bug-report once
> I've triaged this a bit more, but I can recreate your breakage if I start
> a new git database and create two files in the root, and move data between
> 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. :-)
-- Joe
-
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