summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorKaushik Lingarkar <kaushikl@codeaurora.org>2020-12-07 08:40:59 -0700
committerGerrit Code Review <noreply-gerritcodereview@google.com>2020-12-07 15:40:59 +0000
commitcfd99e4be6da02d7a6397496e3b22856d34f8af5 (patch)
tree439d51a978145d7fa294ec252a8ac8531302b250
parente6c0142c176da2b81ca77f52def86699f8aa055e (diff)
Update git submodules
* Update plugins/replication from branch 'stable-2.16' to ba2c8e16b798c2eaf4e56dd66d8c1cd00999e096 - Fix replication to retry on lock errors Versions of Git released since 2014 have created a new status "failed to update ref" which replaces the two statuses "failed to lock" and "failed to write". So, we now see the newer status when the remote is unable to lock a ref. Refer Git commit: https://github.com/git/git/commit/6629ea2d4a5faa0a84367f6d4aedba53cb0f26b4 Config 'lockErrorMaxRetries' is not removed as part of this change as folks who have it configured currently don't run into unexpected behavior with retries when they upgrade to a newer version of the plugin. Also, the "failed to lock" check is not removed for folks still using a version of Git older than 2014. Change-Id: I9b3b15bebd55df30cbee50a0e0c2190d04f2f443
m---------plugins/replication0
1 files changed, 0 insertions, 0 deletions
diff --git a/plugins/replication b/plugins/replication
-Subproject 8fdb0f9ac0a7f68b3f942cb4a9fd4c94e488ab5
+Subproject ba2c8e16b798c2eaf4e56dd66d8c1cd00999e09