git_config_set_multivar_in_file(): avoid call to rollback_lock_file()
After commit_lock_file() is called, then the lock_file object is necessarily either committed or rolled back. So there is no need to call rollback_lock_file() again in either of these cases. Signed-off-by: Michael Haggerty <mhagger@alum.mit.edu> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Michael Haggerty committed
Oct 1, 2014 at 12:28 UTC
e831855ecc6783bfe4b681017349c623fc2fe8c8
1 file changed
+1
config.c
+1
@@ -2083,6 +2083,7 @@ int git_config_set_multivar_in_file(const char *config_filename,
2083
if (commit_lock_file(lock) < 0) {
2084
error("could not commit config file %s", config_filename);
2085
ret = CONFIG_NO_WRITE;
2086
+ lock = NULL;
2087
goto out_free;
2088
}
2089