Re: GSoC draft proposal: Line-level history browser

From: Junio C Hamano <gitster@pobox.com>
Date: Mar 20, 2010, 13:30 UTC
Message-ID: <7vaau3ruhc.fsf@alter.siamese.dyndns.org>
In-Reply-To: <41f08ee11003200610n2c7c9684l6ca200cffdfdb434@mail.gmail.com>

Bo Yang <struggleyb.nku@gmail.com> writes:

> But notice that, detect code movement in one commit is much efficient
> than detecting code copy. So, I think we should add an option to
> control whether we detect such kind of code copy.

If you are hooking into "git log", it already has "-M / -C / -C -C" as a notion to express "different levels of digging" to find code movement and copies, and so does "git blame". You probably will save a lot of time if you studied the current blame implementation thouroughly before designing or coding.

Two things that you need to think about carefully is why "blame" stops at the commits it shows, and if you could "peel" these lines in its output to peek what are behind the lines, what you would see. This is not a rocket science topic, but it is not entirely trivial.