| commit | 40e0dc17ce6f8b699c0f9426438362ed658293dc | |
| author | Johannes Sixt <j6t@kdbg.org> | |
| Tue, 20 Sep 2016 06:18:25 +0000 (20 08:18 +0200) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Wed, 21 Sep 2016 21:09:54 +0000 (21 14:09 -0700) | ||
| tree | 8344b524b433ab3a236dccb86e88925d9a757c95 | treesnapshot (tar.gz zip) |
| parent | b07ad46432aa4fd80e8ebbcc48d38ec94ae20b01 | commitdiff |
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>
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>
| t/t3700-add.sh | diffblobblamehistory |