From: bugzilla-daemon@kernel.org
To: linux-man@vger.kernel.org
Subject: [Bug 215738] uri.7: CONFORMING TO: Refers to obsolete IETF RFC 2396
Date: Sat, 14 May 2022 15:02:28 +0000 [thread overview]
Message-ID: <bug-215738-11311-if5pcuLRwg@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215738-11311@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=215738
--- Comment #4 from sowani@gmail.com ---
(In reply to Alejandro Colomar (man-pages) from comment #3)
> But does the manual page really conform to the newer RFCs? The contents are
> quite large, and I don't know if some details of it are actually obsolete
> and should be fixed.
Actually, it conforms more to rfc8820. So, IMHO, reference to rfc6874 can be
removed. If this sounds okay, I will commit a new patch.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2022-05-14 15:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-24 12:04 [Bug 215738] New: uri.7: CONFORMING TO: Refers to obsolete IETF RFC 2396 bugzilla-daemon
2022-03-24 12:28 ` [Bug 215738] " bugzilla-daemon
2022-05-14 14:30 ` bugzilla-daemon
2022-05-14 14:55 ` bugzilla-daemon
2022-05-14 15:02 ` bugzilla-daemon [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=bug-215738-11311-if5pcuLRwg@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-man@vger.kernel.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