git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: using git-blame with patches as input

From
Junio C Hamano <gitster@pobox.com>
Date
Jun 16, 2008, 22:08 UTC
Message-ID
<7v4p7t9gov.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<7vabhl9hap.fsf@gitster.siamese.dyndns.org>
Junio C Hamano <gitster@pobox.com> writes:
Show 7 quoted lines
> Don Zickus <dzickus@redhat.com> 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).

Previous: Junio C HamanoNext: Don Zickus
Message 5 of 6 in “using git-blame with patches as input”
  1. Don ZickusJun 16, 2008
  2. Junio C HamanoJun 16, 2008
  3. Don ZickusJun 17, 2008
  4. Junio C HamanoJun 16, 2008
  5. Junio C HamanoJun 16, 2008
  6. Don ZickusJun 17, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.