Update git submodules

* Update plugins/replication from branch 'stable-3.2'
  to 5bd0d7e8e5704b11a95a0f2ca4c67eb392002484
  - Merge branch 'stable-3.1' into stable-3.2
    
    * stable-3.1:
      Fix replication to retry on lock errors
    
    Change-Id: Icacd9095feaefd240803405c5b0a16cc0b3a9ed8
    
  - Merge branch 'stable-3.0' into stable-3.1
    
    * stable-3.0:
      Fix replication to retry on lock errors
    
    Change-Id: Ib4b2c1fcac5da6551f72bce68a101b93e9b43b19
    
  - 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
    

1 files changed, 0 insertions, 0 deletions

diff --git a/plugins/replication b/plugins/replication
-Subproject ada8228a735d80a0a8652761621ca1d8c5ba986
+Subproject 5bd0d7e8e5704b11a95a0f2ca4c67eb39200248