Re: using git-blame with patches as input

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Junio C Hamano
Date: Monday, June 16, 2008 - 3:08 pm

Junio C Hamano <gitster@pobox.com> writes:


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@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
using git-blame with patches as input, Don Zickus, (Mon Jun 16, 2:35 pm)
Re: using git-blame with patches as input, Junio C Hamano, (Mon Jun 16, 2:45 pm)
Re: using git-blame with patches as input, Junio C Hamano, (Mon Jun 16, 2:54 pm)
Re: using git-blame with patches as input, Junio C Hamano, (Mon Jun 16, 3:08 pm)
Re: using git-blame with patches as input, Don Zickus, (Tue Jun 17, 7:15 am)
Re: using git-blame with patches as input, Don Zickus, (Tue Jun 17, 7:17 am)