summaryrefslogtreecommitdiff
path: root/copy.c
diff options
context:
space:
mode:
authorMichael Haggerty <mhagger@alum.mit.edu>2014-10-01 12:28:16 +0200
committerJunio C Hamano <gitster@pobox.com>2014-10-01 13:45:11 -0700
commit91f1f1918430f1ee6f9923d949e1543c49f63204 (patch)
tree3f894b0d2aa84aa740c7999ea78245b714b76c1b /copy.c
parent7108ad232fc7a4c889e82b40c52125adc9796ff5 (diff)
downloadgit-91f1f1918430f1ee6f9923d949e1543c49f63204.tar.gz
delete_ref_loose(): don't muck around in the lock_file's filename
It's bad manners. Especially since there could be a signal during the call to unlink_or_warn(), in which case the signal handler will see the wrong filename and delete the reference file, leaving the lockfile behind. So make our own copy to work with. Signed-off-by: Michael Haggerty <mhagger@alum.mit.edu> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'copy.c')
0 files changed, 0 insertions, 0 deletions