Thread (1 message) 1 message, 1 author, 2016-06-15

Re: using git-blame with patches as input

From: Junio C Hamano <hidden>
Date: 2016-06-15 22:44:46

Junio C Hamano [off-list ref] writes:
Don Zickus [off-list ref] writes:
...
quoted
...  Unfortunately, I don't quite understand
some of the algorithms git-blame does when it splits the patch chunks into
smaller pieces to determine which pieces are blame-able on the parents.
http://thread.gmane.org/gmane.comp.version-control.git/28826
In the article quoted, "blame" refers to a very old "git-blame" code that
does not in our codebase anymore.  It talks about "git-pickaxe" which
later took over the "git-blame" name, which happend in acca687
(git-pickaxe: retire pickaxe, 2006-11-08).

It talks about "NEEDSWORK" to hint that the implementation was incomplete,
refering to the version that eventually lead to cee7f24 (git-pickaxe:
blame rewritten., 2006-10-19).
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help