===== git log ====
commit 95f167483e5e88866fef1193a7b7e8c62e2cc065
Author: Rinku Kothiya <rkothiya@redhat.com>
Date:   Mon Jul 20 14:28:20 2020 +0000

    doc: Added release 7.7 notes
    
    Fixes: #1315
    
    Change-Id: I722f540428058f1ac2f3a476d0c374551d8bc283
    Signed-off-by: Rinku Kothiya <rkothiya@redhat.com>

commit c5159b8da1462a8d56188bbec48be95b742a4709
Author: Krutika Dhananjay <kdhananj@redhat.com>
Date:   Thu Sep 12 11:07:10 2019 +0530

    features/shard: Convert shard block indices to uint64
    
    This patch fixes a crash in FOPs that operate on really large sharded
    files where number of participant shards could sometimes exceed
    signed int32 max.
    
    The patch also adds GF_ASSERTs to ensure that number of participating
    shards is always greater than 0 for files that do have more than one
    shard.
    
    Change-Id: I354de58796f350eb1aa42fcdf8092ca2e69ccbb6
    Fixes: #1348
    Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
    (cherry picked from commit cdf01cc47eb2efb427b5855732d9607eec2abc8a)

commit 328f909ca81274843fba76e82f96712998d02b66
Author: Csaba Henk <csaba@redhat.com>
Date:   Fri May 8 23:01:04 2020 +0200

    fuse: occasional logging for fuse device 'weird' write errors
    
    This change is a followup to
    I510158843e4b1d482bdc496c2e97b1860dc1ba93.
    
    In referred change we pushed log messages about 'weird'
    write errors to fuse device out of sight, by reporting
    them at Debug loglevel instead of Error (where
    'weird' means errno is not POSIX compliant but having
    meaningful semantics for FUSE protocol).
    
    This solved the issue of spurious error reporting.
    And so far so good: these messages don't indicate
    an error condition by themselves. However, when they
    come in high repetitions, that indicates a suboptimal

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