public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx.manpages@gmail.com>
To: linux-man@vger.kernel.org
Cc: Alejandro Colomar <alx.manpages@gmail.com>,
	NGINX Unit <unit@nginx.org>, Jakub Wilk <jwilk@jwilk.net>
Subject: [PATCH] uri.7: Update RFC reference (2718 -> 7595)
Date: Mon, 28 Mar 2022 20:56:22 +0200	[thread overview]
Message-ID: <20220328185621.7650-1-alx.manpages@gmail.com> (raw)

There's no significant change that affects this paragraph,
so simply update the reference to the obsolete RFC,
to refer to the current one.

Cc: NGINX Unit <unit@nginx.org>
Cc: Jakub Wilk <jwilk@jwilk.net>
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
---
 man7/uri.7 | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/man7/uri.7 b/man7/uri.7
index 50121b24e..a2401b0cf 100644
--- a/man7/uri.7
+++ b/man7/uri.7
@@ -517,7 +517,7 @@ path, but the two are equivalent for an HTTP URI.
 .PP
 For URIs which must handle characters outside the US ASCII character set,
 the HTML 4.01 specification (section B.2) and
-IETF RFC\ 2718 (section 2.2.5) recommend the following approach:
+IETF RFC\~7595 (section 3.6) recommend the following approach:
 .IP 1. 4
 translate the character sequences into UTF-8 (IETF RFC\~3629)\(emsee
 .BR utf\-8 (7)\(emand
-- 
2.30.2


             reply	other threads:[~2022-03-28 18:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-28 18:56 Alejandro Colomar [this message]
2022-03-28 22:29 ` [PATCH] uri.7: Update RFC reference (2718 -> 7595) Jakub Wilk
2022-04-02 21:29   ` Alejandro Colomar (man-pages)

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=20220328185621.7650-1-alx.manpages@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=jwilk@jwilk.net \
    --cc=linux-man@vger.kernel.org \
    --cc=unit@nginx.org \
    /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