From: bugzilla-daemon@kernel.org
To: linux-man@vger.kernel.org
Subject: [Bug 215613] New: uri.7: DESCRIPTION: Usage: No description of the 'unix' URI scheme
Date: Wed, 16 Feb 2022 15:31:41 +0000 [thread overview]
Message-ID: <bug-215613-11311@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=215613
Bug ID: 215613
Summary: uri.7: DESCRIPTION: Usage: No description of the
'unix' URI scheme
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
The subsection DESCRIPTION/Usage provides a description of common schemes in
use on UNIX-like systems, but there's no mention of the 'unix:' scheme for Unix
domain sockets.
AFAIK, it uses the same format as 'file:' (which is documented), but I don't
know if there are any differences.
--
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-02-16 15:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-16 15:31 bugzilla-daemon [this message]
2022-02-17 20:55 ` [Bug 215613] uri.7: DESCRIPTION: Usage: No description of the 'unix' URI scheme 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-215613-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox