linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Vegard Nossum <vegard.nossum@oracle.com>
Cc: linux-doc@vger.kernel.org
Subject: Re: [PATCH] docs: path-lookup: fix HTML entity mojibake
Date: Mon, 27 Jul 2020 16:14:41 -0600	[thread overview]
Message-ID: <20200727161441.42b0e1c5@lwn.net> (raw)
In-Reply-To: <20200727114527.23944-1-vegard.nossum@oracle.com>

On Mon, 27 Jul 2020 13:45:27 +0200
Vegard Nossum <vegard.nossum@oracle.com> wrote:

> Two cases of "<" somehow turned into "&lt;". I noticed it on
> <https://www.kernel.org/doc/html/latest/filesystems/path-lookup.html>.
> 
> I've verified that the HTML output is correct with this patch.
> 
> Signed-off-by: Vegard Nossum <vegard.nossum@oracle.com>
> ---
>  Documentation/filesystems/path-lookup.rst | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/Documentation/filesystems/path-lookup.rst b/Documentation/filesystems/path-lookup.rst
> index f46b05e9b96c8..1a8fae5036b34 100644
> --- a/Documentation/filesystems/path-lookup.rst
> +++ b/Documentation/filesystems/path-lookup.rst
> @@ -76,10 +76,10 @@ tempting to consider that to have an empty final component.  In many
>  ways that would lead to correct results, but not always.  In
>  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_
> +ending in "``/``".  According to POSIX_:
>  
> -  A pathname that contains at least one non- &lt;slash> character and
> -  that ends with one or more trailing &lt;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

Strange, I wonder how that got through...applied thanks.  

I've applied the other two as well.

jon

      reply	other threads:[~2020-07-27 22:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-27 11:45 [PATCH] docs: path-lookup: fix HTML entity mojibake Vegard Nossum
2020-07-27 22:14 ` Jonathan Corbet [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=20200727161441.42b0e1c5@lwn.net \
    --to=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=vegard.nossum@oracle.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;
as well as URLs for NNTP newsgroup(s).