summaryrefslogtreecommitdiff
path: root/lockfile.c
diff options
context:
space:
mode:
authorAlex Riesen <raa.lkml@gmail.com>2009-04-29 21:21:46 (GMT)
committerJunio C Hamano <gitster@pobox.com>2009-04-30 01:37:41 (GMT)
commitfc71db39e0d75e8a403f36f3fecf4450886cd165 (patch)
treeea69404a0a4afc9417e39e4dcf3e09dca08b4008 /lockfile.c
parentd1c8c0c8c42912eb768a05115c798de50e595f8b (diff)
downloadgit-fc71db39e0d75e8a403f36f3fecf4450886cd165.zip
git-fc71db39e0d75e8a403f36f3fecf4450886cd165.tar.gz
git-fc71db39e0d75e8a403f36f3fecf4450886cd165.tar.bz2
Introduce an unlink(2) wrapper which gives warning if unlink failed
This seem to be a very common pattern in the current code. The function prints a generic removal failure message, the file name which failed and readable errno presentation. The function preserves errno and always returns the value unlink(2) returned, but prints no message for ENOENT, as it was the most often filtered out in the code calling unlink. Besides, removing a file is anyway the purpose of calling unlink. Signed-off-by: Alex Riesen <raa.lkml@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'lockfile.c')
0 files changed, 0 insertions, 0 deletions