summaryrefslogtreecommitdiff
path: root/t/t6100-rev-list-in-order.sh
diff options
context:
space:
mode:
authorLibravatar Johannes Schindelin <johannes.schindelin@gmx.de>2018-08-13 04:33:24 -0700
committerLibravatar Junio C Hamano <gitster@pobox.com>2018-08-13 10:44:51 -0700
commit0b91faa010e438c4e0a58706573f3777da86ecde (patch)
tree1366839fbdd17b4a1cf00e84cc40a534200cfa19 /t/t6100-rev-list-in-order.sh
parentrange-diff: offer to dual-color the diffs (diff)
downloadtgif-0b91faa010e438c4e0a58706573f3777da86ecde.tar.xz
range-diff --dual-color: skip white-space warnings
When displaying a diff of diffs, it is possible that there is an outer `+` before a context line. That happens when the context changed between old and new commit. When that context line starts with a tab (after the space that marks it as context line), our diff machinery spits out a white-space error (space before tab), but in this case, that is incorrect. Rather than adding a specific whitespace flag that specifically ignores the first space in the output (and might miss other problems with the white-space warnings), let's just skip handling white-space errors in dual color mode to begin with. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t6100-rev-list-in-order.sh')
0 files changed, 0 insertions, 0 deletions