Re: GSoC draft proposal: Line-level history browser

Hi,

quoted

4. Code copy of modified file in one commit.

You mean code copy from somewhere in the same file?

I am sorry not. I mean, lines copied from other files that were
modified in the same commit. Just what 'blame' means with one '-C'
options.

quoted

5. Code copy of any place in one commit tree.
6. Fuzzy matching support.

For fuzzy matching support, I would add some ideas, such as trying to
match alpha-numeric characters, or matching longest words or some such.
Also mention the possibility that this might be infeasible. In any case,
give an example what case this is trying to help with.

I think fuzzy matching is used to track multiple lines of
copy/movement, even with little change of the source.
For example, one C function is moved from file1 to file2 and get
renamed. In this case, most of the origin code of function body will
remain unchanged except the function name. So, simply compare the new
added lines with original code line by line and permit some percent of
mismatch will help to find this kind of movement.


Regards!
Bo