diff options
author | Michael Haggerty <mhagger@alum.mit.edu> | 2014-10-01 12:28:21 +0200 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2014-10-01 13:45:13 -0700 |
commit | 8a1c7533e2ee468a505656abab364780b15004fc (patch) | |
tree | 59186c6a8bf85d653d1075842ffbfaff61ca898d /progress.c | |
parent | commit_lock_file(): inline temporary variable (diff) | |
download | tgif-8a1c7533e2ee468a505656abab364780b15004fc.tar.xz |
commit_lock_file(): die() if called for unlocked lockfile object
It was previously a bug to call commit_lock_file() with a lock_file
object that was not active (an illegal access would happen within the
function). It was presumably never done, but this would be an easy
programming error to overlook. So before continuing, do a consistency
check that the lock_file object really is locked.
Helped-by: Johannes Sixt <j6t@kdbg.org>
Signed-off-by: Michael Haggerty <mhagger@alum.mit.edu>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'progress.c')
0 files changed, 0 insertions, 0 deletions