From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: "Pádraig Brady" <P@draigBrady.com>,
"linux-man@vger.kernel.org" <linux-man@vger.kernel.org>
Cc: Gnulib bugs <bug-gnulib@gnu.org>, Coreutils <coreutils@gnu.org>,
Andreas Schwab <schwab@linux-m68k.org>,
"Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>,
Ian Kent <raven@themaw.net>, David Howells <dhowells@redhat.com>,
Al Viro <viro@zeniv.linux.org.uk>,
Colin Walters <walters@redhat.com>,
Ondrej Holy <oholy@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Neil Brown <neilb@suse.com>, Paul Eggert <eggert@cs.ucla.edu>
Subject: Re: [PATCH] fix descriptions for AT_NO_AUTOMOUNT
Date: Mon, 14 Mar 2022 23:16:48 +0100 [thread overview]
Message-ID: <12444329-b272-373c-4255-e39584a6716e@gmail.com> (raw)
In-Reply-To: <9488e311-ab35-96ee-7791-ec65fa6fe948@gmail.com>
Hi Pádraig,
On 3/14/22 20:56, Alejandro Colomar (man-pages) wrote:
> Please send the patch inline (or both inline and attached),
> if you don't mind.
> However, if it's a big hassle for you,
> I can apply it from an attachment.
Thanks for the inline patcx.
> ---
>
>>
>> Subject: [PATCH] fix descriptions for AT_NO_AUTOMOUNT
>>
[...]
>>
>> Signed-off-by: Pádraig Brady <P@draigBrady.com>
>
> Makes sense to me.
> But see a few minor comments below.
But you missed the comments below :)
Please fix them (see below).
Thanks,
Alex
[...]
>> diff --git a/man2/statx.2 b/man2/statx.2
>> index 04b3e5075..d4e638756 100644
>> --- a/man2/statx.2
>> +++ b/man2/statx.2
>> @@ -195,11 +195,23 @@ Don't automount the terminal ("basename") component of
>> if it is a directory that is an automount point.
>> This allows the caller to gather attributes of an automount point
>> (rather than the location it would mount).
>> -This flag can be used in tools that scan directories
>> -to prevent mass-automounting of a directory of automount points.
>> +This
>> +flag has no effect if the mount point has already been mounted over.
>
> Weird break point there.
> I see that it was like that in existing code, but please fix it :)
check
>
>> +.IP
>> The
>> .B AT_NO_AUTOMOUNT
>> -flag has no effect if the mount point has already been mounted over.
>> +flag can be used in tools that scan directories
>> +to prevent mass-automounting of a directory of automount points.
>> +.IP
>> +All of
>> +.BR stat () ,
>
> s/() ,/(2),/
check
>
>> +.BR lstat () ,
>
> s/() ,/(2),/
check
>
>> +and
>> +.BR fstatat ()
>
> s/()/(2)/
check
>
>> +act as though
>> +.B AT_NO_AUTOMOUNT
>> +was set.
>> +.IP
>> This flag is Linux-specific; define
>> .B _GNU_SOURCE
>> .\" Before glibc 2.16, defining _ATFILE_SOURCE sufficed
>> --
>> 2.31.1
>>
>
>
--
Alejandro Colomar
Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/
next prev parent reply other threads:[~2022-03-14 22:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ed3ac15c-9e92-73b7-b7f9-8281488e8778@draigBrady.com>
[not found] ` <3a4c9f63-0203-a810-6113-5c77a16e3690@cs.ucla.edu>
[not found] ` <95140173-2913-e377-5824-8a569ac78b5b@draigBrady.com>
[not found] ` <5c608ef7-f279-6afc-37f5-6a50442a3143@cs.ucla.edu>
[not found] ` <bdd68a31-ef3a-f022-bc72-c051690cee59@draigBrady.com>
[not found] ` <6645f678-4293-4692-8472-eee0bacee63f@cs.ucla.edu>
[not found] ` <670898ee-3b1c-97cd-290c-b6d91bfdaa07@draigBrady.com>
[not found] ` <5612cf59-a6da-6974-6a97-e406a4f4d557@cs.ucla.edu>
[not found] ` <87bkyemetm.fsf@igel.home>
2022-03-10 13:46 ` [PATCH] fix descriptions for AT_NO_AUTOMOUNT Pádraig Brady
2022-03-10 19:29 ` Paul Eggert
2022-03-14 13:24 ` Alejandro Colomar (man-pages)
2022-03-14 18:02 ` Pádraig Brady
2022-03-14 19:56 ` Alejandro Colomar (man-pages)
2022-03-14 20:00 ` Alejandro Colomar (man-pages)
2022-03-14 21:03 ` Pádraig Brady
2022-03-14 21:26 ` [PATCH] stat.2, statx.2: Fix " Pádraig Brady
2022-03-14 22:16 ` Alejandro Colomar (man-pages) [this message]
2022-03-14 23:07 ` Pádraig Brady
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=12444329-b272-373c-4255-e39584a6716e@gmail.com \
--to=alx.manpages@gmail.com \
--cc=P@draigBrady.com \
--cc=akpm@linux-foundation.org \
--cc=bug-gnulib@gnu.org \
--cc=coreutils@gnu.org \
--cc=dhowells@redhat.com \
--cc=eggert@cs.ucla.edu \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=neilb@suse.com \
--cc=oholy@redhat.com \
--cc=raven@themaw.net \
--cc=schwab@linux-m68k.org \
--cc=viro@zeniv.linux.org.uk \
--cc=walters@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox