projects / git.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: c0f5c69) | patch
diff --check: explain why we do not care whether old side is binary
authorJunio C Hamano <gitster@pobox.com>
Thu, 26 Jun 2008 22:34:54 +0000 (15:34 -0700)
committerJunio C Hamano <gitster@pobox.com>
Fri, 27 Jun 2008 01:13:49 +0000 (18:13 -0700)
commit5ff10dd602f5926f0f5a73ae7de5866713428aa7
tree1ae8e0809f42eedd3088da31f14eb6cf28739fe7tree | snapshot
parentc0f5c69c680395a45294184dcf0923cea530b9afcommit | diff
diff --check: explain why we do not care whether old side is binary

All other codepaths refrain from running textual diff when either the old
or the new side is binary, but this function only checks the new side.  I
was almost going to change it to check both, but that would be a bad
change.  Explain why to prevent future mistakes.

Signed-off-by: Junio C Hamano <gitster@pobox.com>
diff.c diff | blob | history
Git—the stupid content tracker