===== git log ====
commit 630b896166fe7d718958bcf57faad4985572ea05
Author: Hari Gowtham <hgowtham@redhat.com>
Date:   Thu May 23 17:13:04 2019 +0530

    doc: Added release notes for 6.2
    
    Fixes: bz#1701203
    
    Change-Id: Id105192610726e370fa977df2c29723201b94695
    Signed-off-by: Hari Gowtham <hgowtham@redhat.com>

commit fa8c8a3fa8bc217bc869fb3db09cb49c6457e402
Author: Kotresh HR <khiremat@redhat.com>
Date:   Tue May 14 11:05:45 2019 +0530

    geo-rep: Convert gfid conflict resolutiong logs into debug
    
    The gfid conflict resolution code path is not supposed
    to hit in generic code path. But few of the heavy rename
    workload (BUG: 1694820) makes it a generic case. So
    logging the entries to be fixed as INFO floods the log
    in these particular workloads. Hence convert them to DEBUG.
    
    Backport of:
     > Patch: https://review.gluster.org/22720
     > BUG: 1709653
     > Change-Id: I4d5e102b87be5fe5b54f78f329e588882d72b9d9
     > Signed-off-by: Kotresh HR <khiremat@redhat.com>
    
    fixes: bz#1712223
    Change-Id: I4d5e102b87be5fe5b54f78f329e588882d72b9d9
    Signed-off-by: Kotresh HR <khiremat@redhat.com>

commit 60df33ab0b7d57e3945d70ed933a5091c4d0b86c
Author: Kotresh HR <khiremat@redhat.com>
Date:   Wed May 8 11:26:06 2019 +0530

    geo-rep: Fix sync hang with tarssh
    
    Problem:
    Geo-rep sync hangs when tarssh is used as sync
    engine at heavy workload.
    
    Analysis and Root cause:
    It's found out that the tar process was hung.
    When debugged further, it's found out that stderr
    buffer of tar process on master was full i.e., 64k.
    When the buffer was copied to a file from /proc/pid/fd/2,
    the hang is resolved.

More commit messages for this ChangeLog can be found at
https://forge.gluster.org/glusterfs-core/glusterfs/commits/v6.2
