Re: using git-blame with patches as input

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Junio C Hamano <gitster@xxxxxxxxx> writes:

> Don Zickus <dzickus@xxxxxxxxxx> writes:
> ...
>> ...  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).
--
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

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux