From: Alejandro Colomar <alx@kernel.org>
To: linux-man@vger.kernel.org
Cc: Alejandro Colomar <alx@kernel.org>
Subject: [PATCH v1 0/2] Document _Fork(3); update fork(2) for POSIX.1-2024
Date: Sat, 17 May 2025 14:16:12 +0200 [thread overview]
Message-ID: <cover.1747484082.git.alx@kernel.org> (raw)
Hi!
I just realized about the existence of _Fork(). I've written a page
documenting it, and updated the existing documentation about fork(2).
Please check.
Have a lovely day!
Alex
Alejandro Colomar (2):
man/man3/_Fork.3: Document _Fork()
man/: Update references to fork(2), and add references to _Fork(3),
for POSIX.1-2024
man/man2/fork.2 | 7 ++++++-
man/man2/vfork.2 | 1 +
man/man3/_Fork.3 | 29 +++++++++++++++++++++++++++++
man/man7/signal-safety.7 | 14 +-------------
4 files changed, 37 insertions(+), 14 deletions(-)
create mode 100644 man/man3/_Fork.3
Range-diff against v0:
-: --------- > 1: a90d0f4c8 man/man3/_Fork.3: Document _Fork()
-: --------- > 2: 2e5dd2415 man/: Update references to fork(2), and add references to _Fork(3), for POSIX.1-2024
--
2.49.0
next reply other threads:[~2025-05-17 12:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-17 12:16 Alejandro Colomar [this message]
2025-05-17 12:16 ` [PATCH v1 1/2] man/man3/_Fork.3: Document _Fork() Alejandro Colomar
2025-05-17 12:16 ` [PATCH v1 2/2] man/: Update references to fork(2), and add references to _Fork(3), for POSIX.1-2024 Alejandro Colomar
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=cover.1747484082.git.alx@kernel.org \
--to=alx@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