Re: GSoC draft proposal: Line-level history browser

Hi,

quoted

Note that, the history may not always be a single thread of commits.
If there are more than one commit which produce the specified line
range, the thread of history will split.

Do not forget the case where there are more than one source of a code
move. Think "refactoring".

Yeah, I really ignore such a condition. Thanks a lot!
And any new added code can be moved/copied from multiple source. This
will really be a new problem for the fuzzy matching.

quoted

=====Work and technical issues=====
==Command options==
This new feature should be used for exploring the history of changes
for certain line range of code in one file.

git log [-m<num>] [-I] [-d depth] [--fuzzy]  -L file1@rev1:<start
pos>,<end pos>  file2@rev2:<start pos>,<end pos>

I would like this not to be specified too much here. For example, we do
not know yet, whether the matching will be fuzzy, or whether we find
something cleverer than that.

Ok, I will focus on express what I will support instead of command line options.

quoted

=====Milestones and Timeline=====
In this summer, we will add support of line level history browser for
only one file. The multiple ranges support is currently not in this
project.

The milestones of the project are:
1. Simple modification change history.

IMHO this should be split into

       1a) have an initial version which does nothing else than parse
           git-log options and a single additional -L, requiring exactly
           one file to be specified

       1b) implement the xdiff callback and identify the commits touching
           the line range (this is not completely trivial due to merges)

I will make a more specified milestones and timeline, thanks!

Regards!
Bo