git blame [was: git and bzr]
- From
- Joseph Wakeling <joseph.wakeling@webdrake.net>
- Date
- Nov 29, 2006, 12:17 UTC
- Message-ID
- <456D7A76.3080605@webdrake.net>
- In-Reply-To
- <Pine.LNX.4.64.0611281906520.3395@woody.osdl.org>
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
Show 6 quoted lines
> 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