summaryrefslogtreecommitdiff
path: root/tests/diff/stats.c
diff options
context:
space:
mode:
authorKevin Swinton <kevin.swinton@gmail.com>2020-04-18 11:32:56 +0100
committerKevin Swinton <kevin.swinton@gmail.com>2020-04-18 11:32:56 +0100
commite72ade87fdb3acf3cbb6bf6d52cd774d924e0e2c (patch)
treef78524e116f005e04014f12cc732f88d2103adf8 /tests/diff/stats.c
parent918a7d19553a9a4181bf1561b8b828a5f82e60e0 (diff)
downloadlibgit2-e72ade87fdb3acf3cbb6bf6d52cd774d924e0e2c.tar.gz
Fix binary diff showing /dev/null
Fixes issue where a changed binary file's content in the working tree isn't displayed correctly, instead showing an oid of zero, and with its path being reported incorrectly as "/dev/null".
Diffstat (limited to 'tests/diff/stats.c')
-rw-r--r--tests/diff/stats.c3
1 files changed, 1 insertions, 2 deletions
diff --git a/tests/diff/stats.c b/tests/diff/stats.c
index 150355686..8bd72633c 100644
--- a/tests/diff/stats.c
+++ b/tests/diff/stats.c
@@ -298,9 +298,8 @@ void test_diff_stats__binary(void)
{
git_buf buf = GIT_BUF_INIT;
const char *stat =
- " binary.bin | Bin 3 -> 0 bytes\n"
+ " binary.bin | Bin 3 -> 5 bytes\n"
" 1 file changed, 0 insertions(+), 0 deletions(-)\n";
- /* TODO: Actually 0 bytes here should be 5!. Seems like we don't load the new content for binary files? */
diff_stats_from_commit_oid(
&_stats, "8d7523f6fcb2404257889abe0d96f093d9f524f9", false);