From: Randy Dunlap <rdunlap@infradead.org>
To: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>,
Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] doc: remove stray HTML entity in '<slash>'
Date: Tue, 28 Jul 2020 19:14:49 -0700 [thread overview]
Message-ID: <1faef34e-053a-121f-1dc5-333c6b6539cc@infradead.org> (raw)
In-Reply-To: <20200729021120.35901-1-luc.vanoostenryck@gmail.com>
On 7/28/20 7:11 PM, Luc Van Oostenryck wrote:
> An excerpt from POSIX contains three occurrences of '<slash>' but
> the first two are spelled starting with an HTML entity: '<slash>'
>
> Fix this by replacing the stray HTML entity by a '<'.
>
> Signed-off-by: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Hi Luc,
One day late.
Fixed and merged yesterday.
https://lore.kernel.org/linux-doc/20200727114527.23944-1-vegard.nossum@oracle.com/
> ---
> Documentation/filesystems/path-lookup.rst | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/filesystems/path-lookup.rst b/Documentation/filesystems/path-lookup.rst
> index e2ba15146365..d46688d6770d 100644
> --- a/Documentation/filesystems/path-lookup.rst
> +++ b/Documentation/filesystems/path-lookup.rst
> @@ -78,8 +78,8 @@ particular, ``mkdir()`` and ``rmdir()`` each create or remove a directory named
> by the final component, and they are required to work with pathnames
> ending in "``/``". According to POSIX_
>
> - A pathname that contains at least one non- <slash> character and
> - that ends with one or more trailing <slash> characters shall not
> + A pathname that contains at least one non-<slash> character and
> + that ends with one or more trailing <slash> characters shall not
> be resolved successfully unless the last pathname component before
> the trailing <slash> characters names an existing directory or a
> directory entry that is to be created for a directory immediately
>
cheers.
--
~Randy
prev parent reply other threads:[~2020-07-29 2:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-29 2:11 [PATCH] doc: remove stray HTML entity in '<slash>' Luc Van Oostenryck
2020-07-29 2:14 ` Randy Dunlap [this message]
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=1faef34e-053a-121f-1dc5-333c6b6539cc@infradead.org \
--to=rdunlap@infradead.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luc.vanoostenryck@gmail.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