summaryrefslogtreecommitdiff
path: root/check_bindir
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2012-11-27 19:47:46 (GMT)
committerJunio C Hamano <gitster@pobox.com>2012-11-27 21:21:15 (GMT)
commita20d3c0de1f107ddd719a4a9cec3addd56e8444f (patch)
tree3b8ec6c561c328017143fe0fd92476dfcd7676aa /check_bindir
parentaf0ed819c59248bc98f0a572bd4cdcb394f185c7 (diff)
downloadgit-a20d3c0de1f107ddd719a4a9cec3addd56e8444f.zip
git-a20d3c0de1f107ddd719a4a9cec3addd56e8444f.tar.gz
git-a20d3c0de1f107ddd719a4a9cec3addd56e8444f.tar.bz2
diff --stat: move the "total count" logic to the last loop
The diffstat generation logic, with --stat-count limit, is implemented as three loops. - The first counts the width necessary to show stats up to specified number of entries, and notes up to how many entries in the data we need to iterate to show the graph; - The second iterates that many times to draw the graph, adjusts the number of "total modified files", and counts the total added/deleted lines for the part that was shown in the graph; - The third iterates over the remainder and only does the part to count "total added/deleted lines" and to adjust "total modified files" without drawing anything. Move the logic to count added/deleted lines and modified files from the second loop to the third loop. This incidentally fixes a bug. The third loop was not filtering binary changes (counted in bytes) from the total added/deleted as it should. The second loop implemented this correctly, so if a binary change appeared earlier than the --stat-count cutoff, the code counted number of added/deleted lines correctly, but if it appeared beyond the cutoff, the number of lines would have mixed with the byte count in the buggy third loop. Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'check_bindir')
0 files changed, 0 insertions, 0 deletions