Linux-Doc Archive on lore.kernel.org
 help / color / Atom feed
* [PATCH] docs: path-lookup: fix HTML entity mojibake
@ 2020-07-27 11:45 Vegard Nossum
  2020-07-27 22:14 ` Jonathan Corbet
  0 siblings, 1 reply; 2+ messages in thread
From: Vegard Nossum @ 2020-07-27 11:45 UTC (permalink / raw)
  To: Jonathan Corbet, linux-doc; +Cc: Vegard Nossum

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
   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
-- 
2.16.1.72.g5be1f00a9.dirty


^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [PATCH] docs: path-lookup: fix HTML entity mojibake
  2020-07-27 11:45 [PATCH] docs: path-lookup: fix HTML entity mojibake Vegard Nossum
@ 2020-07-27 22:14 ` Jonathan Corbet
  0 siblings, 0 replies; 2+ messages in thread
From: Jonathan Corbet @ 2020-07-27 22:14 UTC (permalink / raw)
  To: Vegard Nossum; +Cc: linux-doc

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, back to index

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-07-27 11:45 [PATCH] docs: path-lookup: fix HTML entity mojibake Vegard Nossum
2020-07-27 22:14 ` Jonathan Corbet

Linux-Doc Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-doc/0 linux-doc/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-doc linux-doc/ https://lore.kernel.org/linux-doc \
		linux-doc@vger.kernel.org
	public-inbox-index linux-doc

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-doc


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git