Description of problem:
Rename committed instances of "nsr" as "jbr"
Version-Release number of selected component (if applicable):
Steps to Reproduce:
REVIEW: http://review.gluster.org/13899 (nsr/jbr: Renaming nsr to jbr) posted (#2) for review on master by Avra Sengupta (email@example.com)
COMMIT: http://review.gluster.org/13899 committed in master by Jeff Darcy (firstname.lastname@example.org)
Author: Avra Sengupta <email@example.com>
Date: Mon Apr 4 14:55:20 2016 +0530
nsr/jbr: Renaming nsr to jbr
As per community consensus, we have decided to rename
nsr to jbr(Journal-Based-Replication). This is the patch
to rename the "nsr" code to "jbr"
Signed-off-by: Avra Sengupta <firstname.lastname@example.org>
Smoke: Gluster Build System <email@example.com>
CentOS-regression: Gluster Build System <firstname.lastname@example.org>
NetBSD-regression: NetBSD Build System <email@example.com>
Reviewed-by: Jeff Darcy <firstname.lastname@example.org>
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.8.0, please open a new bug report.
glusterfs-3.8.0 has been announced on the Gluster mailinglists , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.