summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorNasser Grainawi <nasser@codeaurora.org>2020-12-08 08:35:10 -0700
committerGerrit Code Review <noreply-gerritcodereview@google.com>2020-12-08 15:35:10 +0000
commite746bd26b5830c998cd5091d11c542416b062e5f (patch)
tree88b0fcfa4e224617acf282d4aef6ecf46100e6d1
parentd8ba513fec70e1a70d84fe71970295afa97038cb (diff)
Update git submodules
* Update plugins/replication from branch 'stable-3.0' to 2a600dede934b348173bff26e00f373367a3d142 - Merge branch 'stable-2.16' into stable-3.0 * stable-2.16: Fix replication to retry on lock errors Change-Id: I6e262d2c22d2dcd49b341b3c752d6d8b6c93b32c - 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 4604b01e43c3b4aee3d03cb84945b3238c150ed
+Subproject 2a600dede934b348173bff26e00f373367a3d14