author | Linus Torvalds <torvalds@osdl.org> | |
Wed, 26 Oct 2005 17:27:36 +0000 (10:27 -0700) | ||
committer | Junio C Hamano <junkio@cox.net> | |
Wed, 26 Oct 2005 18:58:24 +0000 (11:58 -0700) | ||
commit | 7ebb6fcafed2a3d47390e6f47ff20a98fe451409 | |
tree | 2ccc66e0795aad2eb16f95616f1704235f8c93ab | tree | snapshot |
parent | b5c367f75c2990650119749a1add5216871ca47a | commit | diff |
Fix what to do and how to detect when hardlinking fails
Recent FAT workaround caused compilation trouble on OpenBSD;
different platforms use different error codes when we try to
hardlink the temporary file to its final location. Existing
Coda hack also checks its own error code, but the thing is,
the case we care about is if link failed for a reason other
than that the final file has already existed (which would be
normal, or it could mean collision). So just check the error
code against EEXIST.
Signed-off-by: Junio C Hamano <junkio@cox.net>
Recent FAT workaround caused compilation trouble on OpenBSD;
different platforms use different error codes when we try to
hardlink the temporary file to its final location. Existing
Coda hack also checks its own error code, but the thing is,
the case we care about is if link failed for a reason other
than that the final file has already existed (which would be
normal, or it could mean collision). So just check the error
code against EEXIST.
Signed-off-by: Junio C Hamano <junkio@cox.net>
sha1_file.c | diff | blob | history |