From: Jonathan Corbet <corbet@lwn.net>
To: Askar Safin <safinaskar@mail.ru>, linux-doc <linux-doc@vger.kernel.org>
Subject: Re: documentation/filesystems/path-lookup: replace "These paths" with "Usually paths"
Date: Wed, 31 Mar 2021 14:20:11 -0600 [thread overview]
Message-ID: <87v997jcsk.fsf@meer.lwn.net> (raw)
In-Reply-To: <1616546322.499771404@f511.i.mail.ru>
Askar Safin <safinaskar@mail.ru> writes:
> Reader may think "These paths" refer to empty paths, so changing to "Usually paths"
>
> Signed-off-by: Askar Safin <safinaskar@mail.ru>
> ---
> diff --git a/Documentation/filesystems/path-lookup.rst b/Documentation/filesystems/path-lookup.rst
> index c482e1619e77..c68d6f275935 100644
> --- a/Documentation/filesystems/path-lookup.rst
> +++ b/Documentation/filesystems/path-lookup.rst
> @@ -57,7 +57,7 @@ example, if you have an open file descriptor on an executable file you
> can execute it by calling `execveat() <execveat_>`_ passing
> the file descriptor, an empty path, and the ``AT_EMPTY_PATH`` flag.
>
> -These paths can be divided into two sections: the final component and
> +Usually paths can be divided into two sections: the final component and
> everything else. The "everything else" is the easy bit. In all cases
> it must identify a directory that already exists, otherwise an error
> such as ``ENOENT`` or ``ENOTDIR`` will be reported.
"Usually" doesn't seem right here - it implies that there are times when
that cannot be done. A better fix seems like just taking "These" out..?
Thanks,
jon
next prev parent reply other threads:[~2021-03-31 20:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-24 0:38 documentation/filesystems/path-lookup: replace "These paths" with "Usually paths" Askar Safin
2021-03-31 20:20 ` Jonathan Corbet [this message]
2021-03-31 21:33 ` Re[2]: " Askar Safin
2021-04-26 14:56 ` Askar Safin
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=87v997jcsk.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=safinaskar@mail.ru \
/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;
as well as URLs for NNTP newsgroup(s).