From: bugzilla-daemon@kernel.org
To: linux-man@vger.kernel.org
Subject: [Bug 218453] Update posixoptions to POSIX.1-2018
Date: Fri, 02 Feb 2024 19:53:52 +0000 [thread overview]
Message-ID: <bug-218453-11311-E3TwsraqA9@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218453-11311@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=218453
--- Comment #1 from Enrique Garcia (cquike@arcor.de) ---
There are also two options that are mentioned as "not in final XG6", so I guess
those ones could also be removed:
--- - _POSIX_FILE_LOCKING - _SC_FILE_LOCKING
--- - _POSIX_MULTI_PROCESS - _SC_MULTI_PROCESS
--
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 prev parent reply other threads:[~2024-02-02 19:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 19:48 [Bug 218453] New: Update posixoptions to POSIX.1-2018 bugzilla-daemon
2024-02-02 19:53 ` bugzilla-daemon [this message]
2024-02-02 20:27 ` [Bug 218453] " bugzilla-daemon
2024-02-02 20:54 ` bugzilla-daemon
2024-02-02 20:55 ` bugzilla-daemon
2024-02-02 21:48 ` 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-218453-11311-E3TwsraqA9@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