author | Junio C Hamano <junkio@cox.net> | |
Sat, 21 Oct 2006 10:30:53 +0000 (03:30 -0700) | ||
committer | Junio C Hamano <junkio@cox.net> | |
Sat, 21 Oct 2006 10:30:53 +0000 (03:30 -0700) | ||
commit | aec8fa1f587d68a0e50ada2720c8dc6e09709a9c | |
tree | f082c5c9ce73f890fb2588963a24857a8fa922a3 | tree | snapshot |
parent | f6c0e191020ad330c06438c144e0ea787ca964fd | commit | diff |
git-pickaxe: swap comparison loop used for -C
When assigning blames for code movements across file boundaries,
we used to iterate over blame entries (i.e. groups of lines to
be blamed) in the outer loop and compared each entry with paths
in the parent commit in an inner loop. This meant that we
opened the blob data from each path number of times.
Reorganize the loop so that we read the same path only once, and
compare it against all relevant blame entries.
This should perform better, but seems to give mixed results,
though.
Signed-off-by: Junio C Hamano <junkio@cox.net>
When assigning blames for code movements across file boundaries,
we used to iterate over blame entries (i.e. groups of lines to
be blamed) in the outer loop and compared each entry with paths
in the parent commit in an inner loop. This meant that we
opened the blob data from each path number of times.
Reorganize the loop so that we read the same path only once, and
compare it against all relevant blame entries.
This should perform better, but seems to give mixed results,
though.
Signed-off-by: Junio C Hamano <junkio@cox.net>
builtin-pickaxe.c | diff | blob | history |