All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-man@vger.kernel.org
Subject: [Bug 215737] uri.7: DESCRIPTION: Character encoding: Reference to obsolete IETF RFCs 2718 and 2279
Date: Mon, 28 Mar 2022 18:57:46 +0000	[thread overview]
Message-ID: <bug-215737-11311-Ybr8pFMO0Y@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215737-11311@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=215737

Alejandro Colomar (man-pages) (alx.manpages@gmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |DOCUMENTED

--- Comment #2 from Alejandro Colomar (man-pages) (alx.manpages@gmail.com) ---
2279:
  2718:
    - It doesn't introduce changes relevant for the manual page.
      Update the reference number with no other changes.

2718:
  7595:
    - It deprecates URL in favor of URI.
      Replace the terms in the manual page,
      which were (sometimes) ambiguously used.
    - It stays the same regarding character encoding.
      Update the reference number with no other changes.
  8615:
    - It doesn't introduce changes relevant for the manual page.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-24 12:01 [Bug 215737] New: uri.7: DESCRIPTION: Character encoding: Reference to obsolete IETF RFCs 2718 and 2279 bugzilla-daemon
2022-03-24 12:16 ` [Bug 215737] " bugzilla-daemon
2022-03-28 18:57 ` 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-215737-11311-Ybr8pFMO0Y@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.