From: bugzilla-daemon@bugzilla.kernel.org
To: linux-man@vger.kernel.org
Subject: [Bug 212385] path_resolution(7): "a pathname with a trailing '/' is equivalent to the pathname obtained by appending '.' to it" - this is wrong
Date: Sun, 08 Aug 2021 23:05:57 +0000 [thread overview]
Message-ID: <bug-212385-11311-XiyFPvTXN2@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-212385-11311@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=212385
Michael Kerrisk (mtk.manpages@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mtk.manpages@gmail.com
--- Comment #1 from Michael Kerrisk (mtk.manpages@gmail.com) ---
Hello Askar. Thanks for the report. Yes, the text is a bit off.
The text in POSIX.1-2018 Section 4.13 ("Pathname Resolution")
is helpful in pointing to a better wording.
How about the following as a replacement text:
If a pathname ends in a '/', that forces resolution of the
preceding component as in Step 2: the component preceding the
slash either exists and resolves to a directory of it names a
directory that is to be created immediately after the
pathname is resolved. Otherwise, a trailing '/' is ignored.
I'm closing this bug report for now. Please reopen if you think something still
needs fixing.
--
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 parent reply other threads:[~2021-08-08 23:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-212385-11311@https.bugzilla.kernel.org/>
2021-08-08 23:05 ` bugzilla-daemon [this message]
2021-08-08 23:26 ` [Bug 212385] path_resolution(7): "a pathname with a trailing '/' is equivalent to the pathname obtained by appending '.' to it" - this is wrong 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-212385-11311-XiyFPvTXN2@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.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