* [PATCH] cifs-utils: mention the kernel version that introduced getcifsacl
@ 2011-10-18 6:36 Suresh Jayaraman
[not found] ` <4E9D1E5D.4020603-l3A5Bk7waGM@public.gmane.org>
0 siblings, 1 reply; 3+ messages in thread
From: Suresh Jayaraman @ 2011-10-18 6:36 UTC (permalink / raw)
To: Jeff Layton; +Cc: linux-cifs, Shirish Pargaonkar
Cc: Shirish Pargaonkar <shirishpargaonkar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Signed-off-by: Suresh Jayaraman <sjayaraman-l3A5Bk7waGM@public.gmane.org>
---
getcifsacl.8.in | 3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/getcifsacl.8.in b/getcifsacl.8.in
index 02e1355..f79f7ff 100644
--- a/getcifsacl.8.in
+++ b/getcifsacl.8.in
@@ -40,6 +40,9 @@ Print version number and exit\&.
.RS 4
Display a security descriptor in raw mode. Values such as type and flags are displayed in hexadecimal format, a SID is not mapped to a name.
.RE
+.SH "NOTES"
+.PP
+Kernel support for getcifsacl/setcifsacl utilities was initially introduced in the 2.6.37 kernel.
.SH "SEE ALSO"
.PP
\fBmount.cifs\fR(8),
^ permalink raw reply related [flat|nested] 3+ messages in thread
* Re: [PATCH] cifs-utils: mention the kernel version that introduced getcifsacl
[not found] ` <4E9D1E5D.4020603-l3A5Bk7waGM@public.gmane.org>
@ 2011-10-18 9:35 ` Shirish Pargaonkar
[not found] ` <CADT32eLiG_oqKEu6dtEXyH6kepMwGt+G_+5OJTxefO8y85oCHA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
0 siblings, 1 reply; 3+ messages in thread
From: Shirish Pargaonkar @ 2011-10-18 9:35 UTC (permalink / raw)
To: sjayaraman-l3A5Bk7waGM; +Cc: Jeff Layton, linux-cifs
On Tue, Oct 18, 2011 at 1:36 AM, Suresh Jayaraman <sjayaraman-l3A5Bk7waGM@public.gmane.org> wrote:
>
> Cc: Shirish Pargaonkar <shirishpargaonkar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> Signed-off-by: Suresh Jayaraman <sjayaraman-l3A5Bk7waGM@public.gmane.org>
> ---
> getcifsacl.8.in | 3 +++
> 1 files changed, 3 insertions(+), 0 deletions(-)
>
> diff --git a/getcifsacl.8.in b/getcifsacl.8.in
> index 02e1355..f79f7ff 100644
> --- a/getcifsacl.8.in
> +++ b/getcifsacl.8.in
> @@ -40,6 +40,9 @@ Print version number and exit\&.
> .RS 4
> Display a security descriptor in raw mode. Values such as type and flags are displayed in hexadecimal format, a SID is not mapped to a name.
> .RE
> +.SH "NOTES"
> +.PP
> +Kernel support for getcifsacl/setcifsacl utilities was initially introduced in the 2.6.37 kernel.
Looks fine. Just a nitpicking, since this is a getcifsacl manpage,
does setcifsacl also need to be mentioned here?
Reviewed-by: Shirish Pargaonkar <shirishpargaonkar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> .SH "SEE ALSO"
> .PP
> \fBmount.cifs\fR(8),
>
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH] cifs-utils: mention the kernel version that introduced getcifsacl
[not found] ` <CADT32eLiG_oqKEu6dtEXyH6kepMwGt+G_+5OJTxefO8y85oCHA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
@ 2011-10-18 10:06 ` Suresh Jayaraman
0 siblings, 0 replies; 3+ messages in thread
From: Suresh Jayaraman @ 2011-10-18 10:06 UTC (permalink / raw)
To: Shirish Pargaonkar; +Cc: Jeff Layton, linux-cifs
On 10/18/2011 03:05 PM, Shirish Pargaonkar wrote:
> On Tue, Oct 18, 2011 at 1:36 AM, Suresh Jayaraman <sjayaraman-l3A5Bk7waGM@public.gmane.org> wrote:
>>
>> Cc: Shirish Pargaonkar <shirishpargaonkar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
>> Signed-off-by: Suresh Jayaraman <sjayaraman-l3A5Bk7waGM@public.gmane.org>
>> ---
>> getcifsacl.8.in | 3 +++
>> 1 files changed, 3 insertions(+), 0 deletions(-)
>>
>> diff --git a/getcifsacl.8.in b/getcifsacl.8.in
>> index 02e1355..f79f7ff 100644
>> --- a/getcifsacl.8.in
>> +++ b/getcifsacl.8.in
>> @@ -40,6 +40,9 @@ Print version number and exit\&.
>> .RS 4
>> Display a security descriptor in raw mode. Values such as type and flags are displayed in hexadecimal format, a SID is not mapped to a name.
>> .RE
>> +.SH "NOTES"
>> +.PP
>> +Kernel support for getcifsacl/setcifsacl utilities was initially introduced in the 2.6.37 kernel.
>
> Looks fine. Just a nitpicking, since this is a getcifsacl manpage,
> does setcifsacl also need to be mentioned here?
The thought behind this was that - though the man pages are different,
users will see them as single facility and would want to use them
together mostly (assumption here is that a user who is reading and using
getcifsacl or setcifsacl would also read and use the other sooner).
Suresh
> Reviewed-by: Shirish Pargaonkar <shirishpargaonkar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
>
>> .SH "SEE ALSO"
>> .PP
>> \fBmount.cifs\fR(8),
>>
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2011-10-18 10:06 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-10-18 6:36 [PATCH] cifs-utils: mention the kernel version that introduced getcifsacl Suresh Jayaraman
[not found] ` <4E9D1E5D.4020603-l3A5Bk7waGM@public.gmane.org>
2011-10-18 9:35 ` Shirish Pargaonkar
[not found] ` <CADT32eLiG_oqKEu6dtEXyH6kepMwGt+G_+5OJTxefO8y85oCHA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-10-18 10:06 ` Suresh Jayaraman
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox