On 06/20/2014 04:43 PM, Ronnie Sahlberg wrote:
lock_ref_sha1 was only called from one place in refc.c and only provided
a check that the refname was sane before adding back the initial "refs/"
part of the ref path name, the initial "refs/" that this caller had already
stripped off before calling lock_ref_sha1.
[...]
I'm especially glad to see this ugly function disappear!
Michael
--
Michael Haggerty
mhagger@alum.mit.edu