summaryrefslogtreecommitdiff
path: root/sequencer.c
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2016-12-19 22:45:35 (GMT)
committerJunio C Hamano <gitster@pobox.com>2016-12-19 22:45:35 (GMT)
commit95713ff4fb858c4f2e7c339cfc503c0cf152e071 (patch)
tree988d8503fff22d5ddcc2d21afb88e05e5f295350 /sequencer.c
parent731490bf06792a4c96b61965cba2a0e430118e78 (diff)
parent3f061bf514667497a948804828064b9b9c3b249b (diff)
downloadgit-95713ff4fb858c4f2e7c339cfc503c0cf152e071.zip
git-95713ff4fb858c4f2e7c339cfc503c0cf152e071.tar.gz
git-95713ff4fb858c4f2e7c339cfc503c0cf152e071.tar.bz2
Merge branch 'jc/lock-report-on-error'
Git 2.11 had a minor regression in "merge --ff-only" that competed with another process that simultanously attempted to update the index. We used to explain what went wrong with an error message, but the new code silently failed. The error message has been resurrected. * jc/lock-report-on-error: lockfile: LOCK_REPORT_ON_ERROR hold_locked_index(): align error handling with hold_lockfile_for_update() wt-status: implement opportunisitc index update correctly
Diffstat (limited to 'sequencer.c')
-rw-r--r--sequencer.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/sequencer.c b/sequencer.c
index 050e28b..28061dc 100644
--- a/sequencer.c
+++ b/sequencer.c
@@ -323,7 +323,7 @@ static int do_recursive_merge(struct commit *base, struct commit *next,
char **xopt;
static struct lock_file index_lock;
- hold_locked_index(&index_lock, 1);
+ hold_locked_index(&index_lock, LOCK_DIE_ON_ERROR);
read_cache();