aboutsummaryrefslogtreecommitdiffstats
path: root/mergetools/vimdiff
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2016-12-19 14:45:35 -0800
committerJunio C Hamano <gitster@pobox.com>2016-12-19 14:45:35 -0800
commit95713ff4fb858c4f2e7c339cfc503c0cf152e071 (patch)
tree988d8503fff22d5ddcc2d21afb88e05e5f295350 /mergetools/vimdiff
parent731490bf06792a4c96b61965cba2a0e430118e78 (diff)
parent3f061bf514667497a948804828064b9b9c3b249b (diff)
downloadgit-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 'mergetools/vimdiff')
0 files changed, 0 insertions, 0 deletions