From: bugzilla-daemon@kernel.org
To: linux-man@vger.kernel.org
Subject: [Bug 215735] New: uri.7: DESCRIPTION: Usage: news: Mention to obsolete IETF RFC 1036
Date: Thu, 24 Mar 2022 11:43:03 +0000 [thread overview]
Message-ID: <bug-215735-11311@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=215735
Bug ID: 215735
Summary: uri.7: DESCRIPTION: Usage: news: Mention to obsolete
IETF RFC 1036
Product: Documentation
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P1
Component: man-pages
Assignee: documentation_man-pages@kernel-bugs.osdl.org
Reporter: alx.manpages@gmail.com
Regression: No
uri(7)::DESCRIPTION::Usage::news reads as:
```
news - Newsgroup or News message
news:newsgroup-name
news:message-id
A newsgroup-name is a period-delimited hierarchical name,
such as "comp.infosystems.www.misc". If <newsgroup-name>
is "*" (as in <news:*>), it is used to refer to "all
available news groups". An example is
<news:comp.lang.ada>.
A message-id corresponds to the Message-ID of IETF
RFC 1036, <http://www.ietf.org/rfc/rfc1036.txt> without
the enclosing "<" and ">"; it takes the form
unique@full_domain_name. A message identifier may be
distinguished from a news group name by the presence of
the "@" character.
```
It refers to an obsolete RFC[1]. We should update the info there.
[1]: <https://www.rfc-editor.org/rfc/rfc1036>
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2022-03-24 11:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-24 11:43 bugzilla-daemon [this message]
2022-03-24 11:50 ` [Bug 215735] uri.7: DESCRIPTION: Usage: news: Reference to obsolete IETF RFC 1036 bugzilla-daemon
2022-03-24 12:32 ` bugzilla-daemon
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-215735-11311@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.