From f3b8a931b00cfd0ecee46599ed1ef1aaf236e148 Mon Sep 17 00:00:00 2001 From: Aravinda VK Date: Fri, 19 Feb 2016 17:08:56 +0530 Subject: 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: 1313310 Change-Id: I83d59831997dbd1264b48e9b1aa732c7dfc700b5 Signed-off-by: Aravinda VK Reviewed-on: http://review.gluster.org/13477 Smoke: Gluster Build System Reviewed-by: Milind Changire NetBSD-regression: NetBSD Build System Reviewed-by: Kotresh HR CentOS-regression: Gluster Build System Reviewed-by: Venky Shankar (cherry picked from commit 1b897c39ba8c0f1bf180316637cc2d87e6920800) Reviewed-on: http://review.gluster.org/13559 --- tools/glusterfind/src/__init__.py | 1 + 1 file changed, 1 insertion(+) (limited to 'tools/glusterfind/src/__init__.py') diff --git a/tools/glusterfind/src/__init__.py b/tools/glusterfind/src/__init__.py index eb941c6d67c..0ffb3f7432d 100644 --- a/tools/glusterfind/src/__init__.py +++ b/tools/glusterfind/src/__init__.py @@ -1,4 +1,5 @@ #!/usr/bin/env python +# -*- coding: utf-8 -*- # Copyright (c) 2015 Red Hat, Inc. # This file is part of GlusterFS. -- cgit