summaryrefslogtreecommitdiff
path: root/Documentation/howto/recover-corrupted-blob-object.txt
diff options
context:
space:
mode:
authorLibravatar Torsten Bögershausen <tboegi@web.de>2015-01-27 16:39:01 +0100
committerLibravatar Junio C Hamano <gitster@pobox.com>2015-02-15 15:48:38 -0800
commitf400e51c13eb4143e420d41d9b415d4f5ddbdb85 (patch)
treeaf669aea9c3316ce32f2499f6b23928ab6955e99 /Documentation/howto/recover-corrupted-blob-object.txt
parenttests: correct misuses of POSIXPERM (diff)
downloadtgif-f400e51c13eb4143e420d41d9b415d4f5ddbdb85.tar.xz
test-lib.sh: set prerequisite SANITY by testing what we really need
What we wanted out of the SANITY precondition is that the filesystem behaves sensibly with permission bits settings. - You should not be able to remove a file in a read-only directory, - You should not be able to tell if a file in a directory exists if the directory lacks read or execute permission bits. We used to cheat by approximating that condition with "is the / writable?" test and/or "are we running as root?" test. Neither test is sufficient or appropriate in environments like Cygwin. Signed-off-by: Torsten Bögershausen <tboegi@web.de> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation/howto/recover-corrupted-blob-object.txt')
0 files changed, 0 insertions, 0 deletions