===== git log ====
commit 7ddcf035b8aa34ccf25ae6a04143a54998673eac
Author: ShyamsundarR <srangana@redhat.com>
Date:   Mon Aug 27 09:02:28 2018 -0400

    doc: Release notes for v4.1.3
    
    Change-Id: Ia944a2353f0a89b61f66bde7f270489dff3793b4
    fixes: bz#1607945
    Signed-off-by: ShyamsundarR <srangana@redhat.com>

commit 95608a9d454fbc83f92aedac400b9580b95dbecc
Author: Jiffin Tony Thottan <jthottan@redhat.com>
Date:   Tue Jul 31 14:52:51 2018 +0530

    gfapi : Handle the path == "" glfs_resolve_at
    
    Currently there is no check for path = "" in glfs_resolve_at.
    So if application sends an empty path, then the function resolves
    into the parent inode which is incorrect. Plus modified possible
    of "path" with "origpath" in the same function.
    
    Change-Id: Ie5ff9ce4b771607b7dbb3fe00704fe670421792a
    fixes: bz#1618347
    Signed-off-by: Jiffin Tony Thottan <jthottan@redhat.com>
    (cherry picked from commit febee007bb1a99d65300630c2a98cbb642b1c8dc)

commit 9de3ccb5ffbc531a4d8ce708a733a861d3dcd3eb
Author: Mark Mielke <mark.mielke@gmail.com>
Date:   Mon Aug 13 23:54:34 2018 -0400

    Bash integration script should namespace variables
    
    In the original submitted script, it looks like there was effort
    put into namespacing all global variables. However a few mistakes
    remained.
    
    GLUSTER_TOP_SUBOPTIONSx were defined, but TOP_SUBOPTIONSx were
    referenced. This was likely an unrecognized defect in the
    original code submission? These are now corrected to refer to
    GLUSTER_TOP_SUBOPTIONSx.
    
    FINAL_LIST, LIST, and TOP were leaked into all Bash shells and
    used by the command completion functions. The most problematic
    of these was TOP, which was declared with "-i" making it an
    integer. This cause other code which used TOP to define a path
    to fail like this:
    
        $ bash
        $ TOP=/abc

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