diff options
| author | Junio C Hamano <gitster@pobox.com> | 2016-12-19 14:45:35 -0800 |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2016-12-19 14:45:35 -0800 |
| commit | 95713ff4fb858c4f2e7c339cfc503c0cf152e071 (patch) | |
| tree | 988d8503fff22d5ddcc2d21afb88e05e5f295350 /merge-recursive.c | |
| parent | 731490bf06792a4c96b61965cba2a0e430118e78 (diff) | |
| parent | 3f061bf514667497a948804828064b9b9c3b249b (diff) | |
| download | git-95713ff4fb858c4f2e7c339cfc503c0cf152e071.tar.gz | |
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 'merge-recursive.c')
| -rw-r--r-- | merge-recursive.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/merge-recursive.c b/merge-recursive.c index 23d6992f40..d327209443 100644 --- a/merge-recursive.c +++ b/merge-recursive.c @@ -2133,7 +2133,7 @@ int merge_recursive_generic(struct merge_options *o, } } - hold_locked_index(lock, 1); + hold_locked_index(lock, LOCK_DIE_ON_ERROR); clean = merge_recursive(o, head_commit, next_commit, ca, result); if (clean < 0) |