summaryrefslogtreecommitdiff
path: root/contrib/examples/git-whatchanged.sh
diff options
context:
space:
mode:
authorLibravatar Johannes Sixt <j6t@kdbg.org>2016-09-20 08:18:25 +0200
committerLibravatar Junio C Hamano <gitster@pobox.com>2016-09-21 14:09:54 -0700
commit40e0dc17ce6f8b699c0f9426438362ed658293dc (patch)
tree8344b524b433ab3a236dccb86e88925d9a757c95 /contrib/examples/git-whatchanged.sh
parentt3700-add: create subdirectory gently (diff)
downloadtgif-40e0dc17ce6f8b699c0f9426438362ed658293dc.tar.xz
t3700-add: do not check working tree file mode without POSIXPERM
A recently introduced test checks the result of 'git status' after setting the executable bit on a file. This check does not yield the expected result when the filesystem does not support the executable bit. What we care about is that a file added with "--chmod=+x" has executable bit in the index and that "--chmod=+x" (or any other options for that matter) does not muck with working tree files. The former is tested by other existing tests, so let's check the latter more explicitly and only under POSIXPERM prerequisite. Signed-off-by: Johannes Sixt <j6t@kdbg.org> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'contrib/examples/git-whatchanged.sh')
0 files changed, 0 insertions, 0 deletions