--dirstat-by-file: Make it faster and more correct
Currently, when using --dirstat-by-file, it first does the full --dirstat analysis (using diffcore_count_changes()), and then resets 'damage' to 1, if any damage was found by diffcore_count_changes(). But --dirstat-by-file is not interested in the file damage per se. It only cares if the file changed at all. In that sense it only cares if the blob object for a file has changed. We therefore only need to compare the object names of each file pair in the diff queue and we can skip the entire --dirstat analysis and simply set 'damage' to 1 for each entry where the object name has changed. This makes --dirstat-by-file faster, and also bypasses --dirstat's practice of ignoring rearranged lines within a file. The patch also contains an added testcase verifying that --dirstat-by-file now detects changes that only rearrange lines within a file. Signed-off-by: Johan Herland <johan@herland.net> Acked-by: Linus Torvalds <torvalds@linux-foundation.org> Signed-off-by: Junio C Hamano <gitster@pobox.com>
This commit is contained in:

committed by
Junio C Hamano

parent
204f01a2f7
commit
0133dab75d
@ -302,6 +302,8 @@ diff master master^ side
|
||||
diff --dirstat master~1 master~2
|
||||
# --dirstat doesn't notice changes that simply rearrange existing lines
|
||||
diff --dirstat initial rearrange
|
||||
# ...but --dirstat-by-file does notice changes that only rearrange lines
|
||||
diff --dirstat-by-file initial rearrange
|
||||
EOF
|
||||
|
||||
test_expect_success 'log -S requires an argument' '
|
||||
|
Reference in New Issue
Block a user