Bug 1414645 - Typo in glusterfs code comments
Summary: Typo in glusterfs code comments
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: core
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
Assignee: Nithya Balachandran
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-01-19 06:35 UTC by Nithya Balachandran
Modified: 2017-05-30 18:38 UTC (History)
2 users (show)

Fixed In Version: glusterfs-3.11.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-05-30 18:38:45 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Nithya Balachandran 2017-01-19 06:35:41 UTC
Description of problem:
Typo: "recieve" should be "receive"

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Worker Ant 2017-01-19 06:55:00 UTC
REVIEW: http://review.gluster.org/16429 (gluster: Typos in logs and comments) posted (#1) for review on master by N Balachandran (nbalacha)

Comment 2 Worker Ant 2017-01-19 20:37:12 UTC
COMMIT: http://review.gluster.org/16429 committed in master by Jeff Darcy (jdarcy) 
------
commit 4e11d50f3f803e685c844da1f168a633c3834fd0
Author: N Balachandran <nbalacha>
Date:   Thu Jan 19 12:23:00 2017 +0530

    gluster: Typos in logs and comments
    
    Replaced 'recieve' with 'receive'.
    
    Change-Id: I4c1c9147db5437feb81e4c83ed074440aaa28e07
    BUG: 1414645
    Signed-off-by: N Balachandran <nbalacha>
    Reviewed-on: http://review.gluster.org/16429
    Smoke: Gluster Build System <jenkins.org>
    Reviewed-by: Manikandan Selvaganesh <manikandancs333>
    Tested-by: Manikandan Selvaganesh <manikandancs333>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>
    Reviewed-by: Jeff Darcy <jdarcy>

Comment 3 Shyamsundar 2017-05-30 18:38:45 UTC
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.11.0, please open a new bug report.

glusterfs-3.11.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://lists.gluster.org/pipermail/announce/2017-May/000073.html
[2] https://www.gluster.org/pipermail/gluster-users/


Note You need to log in before you can comment on or make changes to this bug.