From: Alejandro Colomar <alx@kernel.org>
To: linux-man@vger.kernel.org
Cc: Alejandro Colomar <alx@kernel.org>,
Thomas Orgis <thomas@orgis.org>, Eric Blake <eblake@redhat.com>
Subject: [PATCH 1/2] sigaction.2: HISTORY: SA_NOCLDSTOP wasn't added in POSIX.1-2001
Date: Sun, 25 Feb 2024 12:53:15 +0100 [thread overview]
Message-ID: <20240225115307.438556-2-alx@kernel.org> (raw)
In-Reply-To: <20240225115307.438556-1-alx@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 599 bytes --]
It already existed in POSIX.1-1996, according to just a few lines above.
Cc: Thomas Orgis <thomas@orgis.org>
Cc: Eric Blake <eblake@redhat.com>
Signed-off-by: Alejandro Colomar <alx@kernel.org>
---
man2/sigaction.2 | 1 -
1 file changed, 1 deletion(-)
diff --git a/man2/sigaction.2 b/man2/sigaction.2
index 0bbc44bd5..b64dcaf2b 100644
--- a/man2/sigaction.2
+++ b/man2/sigaction.2
@@ -1020,7 +1020,6 @@ .SH HISTORY
POSIX.1-1990 specified only
.BR SA_NOCLDSTOP .
POSIX.1-2001 added
-.BR SA_NOCLDSTOP ,
.BR SA_NOCLDWAIT ,
.BR SA_NODEFER ,
.BR SA_ONSTACK ,
--
2.43.0
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-02-25 11:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-14 8:57 SA_RESTART and friends as XSI extensions to POSIX.1-2001 < XOPEN_SOURCE >= 600 Thomas Orgis
2024-02-25 11:41 ` Status of SA_NOCLDWAIT in POSIX.1 (was: SA_RESTART and friends as XSI extensions to POSIX.1-2001 < XOPEN_SOURCE >= 600) Alejandro Colomar
2024-02-25 11:53 ` [PATCH 0/2] sigaction.2: HISTORY: Document history of POSIX constants more accurately Alejandro Colomar
2024-02-25 11:53 ` Alejandro Colomar [this message]
2024-02-27 18:12 ` [PATCH 1/2] sigaction.2: HISTORY: SA_NOCLDSTOP wasn't added in POSIX.1-2001 Thomas Orgis
2024-02-27 21:15 ` Alejandro Colomar
2024-02-25 11:53 ` [PATCH 2/2] sigaction.2: HISTORY: Some constants are or were XSI extensions Alejandro Colomar
2024-02-27 18:14 ` Thomas Orgis
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=20240225115307.438556-2-alx@kernel.org \
--to=alx@kernel.org \
--cc=eblake@redhat.com \
--cc=linux-man@vger.kernel.org \
--cc=thomas@orgis.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.