[Bugs] [Bug 1310080] [RFE]Add --no-encode option to the `glusterfind pre` command
bugzilla at redhat.com
bugzilla at redhat.com
Fri Feb 26 10:11:26 UTC 2016
https://bugzilla.redhat.com/show_bug.cgi?id=1310080
--- Comment #4 from Vijay Bellur <vbellur at redhat.com> ---
COMMIT: http://review.gluster.org/13477 committed in master by Venky Shankar
(vshankar at redhat.com)
------
commit 1b897c39ba8c0f1bf180316637cc2d87e6920800
Author: Aravinda VK <avishwan at redhat.com>
Date: Fri Feb 19 17:08:56 2016 +0530
tools/glusterfind: New option --no-encode
New option added to skip encoding path in output file. Also handled
Unicode strings.
File paths can have newline characters, to differentiate between each
path patch is encoded according to
RFC3986(https://www.ietf.org/rfc/rfc3986.txt). Due to this consumer
applications have to decode the path before consuming it. With this
option Paths are not encoded, can be directly consumed by
applications.
Unicode encoding is handled automatically
BUG: 1310080
Change-Id: I83d59831997dbd1264b48e9b1aa732c7dfc700b5
Signed-off-by: Aravinda VK <avishwan at redhat.com>
Reviewed-on: http://review.gluster.org/13477
Smoke: Gluster Build System <jenkins at build.gluster.com>
Reviewed-by: Milind Changire <mchangir at redhat.com>
NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
Reviewed-by: Kotresh HR <khiremat at redhat.com>
CentOS-regression: Gluster Build System <jenkins at build.gluster.com>
Reviewed-by: Venky Shankar <vshankar at redhat.com>
--
You are receiving this mail because:
You are the QA Contact for the bug.
More information about the Bugs
mailing list