git/refs at e6fc267314d24fe9a81875b85b28a4b5d0fb78b1 - git

Tree: e6fc267314

Jeff King 83a3069a38 lockfile: do not rollback lock on failed close Since the lockfile code is based on the tempfile code, it has some of the same problems, including that close_lock_file() erases the tempfile's filename buf, making it hard for the caller to write a good error message. In practice this comes up less for lockfiles than for straight tempfiles, since we usually just report the refname. But there is at least one buggy case in write_ref_to_lockfile(). Besides, given the coupling between the lockfile and tempfile modules, it's less confusing if their close() functions have the same semantics. Just as the previous commit did for close_tempfile(), let's teach close_lock_file() and its wrapper close_ref() not to rollback on error. And just as before, we'll give them new "gently" names to catch any new callers that are added. Signed-off-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>		8 years ago
..
files-backend.c	lockfile: do not rollback lock on failed close	8 years ago
iterator.c	prefix_ref_iterator: don't trim too much	8 years ago
packed-backend.c	lockfile: do not rollback lock on failed close	8 years ago
packed-backend.h	packed_refs_unlock(), packed_refs_is_locked(): new functions	8 years ago
ref-cache.c	*.[ch] refactoring: make use of the FREE_AND_NULL() macro	8 years ago
ref-cache.h	create_ref_entry(): remove `check_name` option	8 years ago
refs-internal.h	Merge branch 'mh/ref-lock-entry'	8 years ago