delete_ref_loose(): don't muck around in the lock_file's filename
commit91f1f1918430f1ee6f9923d949e1543c49f63204
authorMichael Haggerty <mhagger@alum.mit.edu>
Wed, 1 Oct 2014 10:28:16 +0000 (1 12:28 +0200)
committerJunio C Hamano <gitster@pobox.com>
Wed, 1 Oct 2014 20:45:11 +0000 (1 13:45 -0700)
tree3f894b0d2aa84aa740c7999ea78245b714b76c1b
parent7108ad232fc7a4c889e82b40c52125adc9796ff5
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>
refs.c