From 846ca47a2411f33c8ca0572b0e565664d851fee4 Mon Sep 17 00:00:00 2001

From: Kamil Dudka <kdudka@redhat.com>

Date: Fri, 19 Nov 2010 12:40:11 +0100

Subject: [PATCH] setfattr.1: document supported encodings of values

reported by Tomasz Kepczynski at https://bugzilla.redhat.com/58751

---

 man/man1/setfattr.1 |   10 +++++++++-

 1 files changed, 9 insertions(+), 1 deletions(-)

diff --git a/man/man1/setfattr.1 b/man/man1/setfattr.1

index c36b024..2d33f50 100644

--- a/man/man1/setfattr.1

+++ b/man/man1/setfattr.1

@@ -46,7 +46,15 @@ for each specified file.

 Specifies the name of the extended attribute to set.

 .TP

 .BR \-v " \f2value\f1, " \-\-value "=\f2value\f1"

-Specifies the new value for the extended attribute.

+Specifies the new value of the extended attribute. There are three methods

+available for encoding the value.  If the given string is enclosed in double

+quotes, the inner string is treated as text. In that case, backslashes and

+double quotes have special meanings and need to be escaped by a preceding

+backslash. Any control characters can be encoded as a backslash followed by

+three digits as its ASCII code in octal. If the given string begins with 0x or

+0X, it expresses a hexadecimal number. If the given string begins with 0s or

+0S, base64 encoding is expected.  See also the \-\-encoding option of

+getfattr(1).

 .TP

 .BR \-x " \f2name\f1, " \-\-remove "=\f2name\f1"

 Remove the named extended attribute entirely.

-- 

1.7.3.3