From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: linux-man@vger.kernel.org
Cc: alx@kernel.org
Subject: [PATCH 2/6] vfork.2: ffix
Date: Fri, 28 Jul 2023 12:58:55 -0500 [thread overview]
Message-ID: <20230728175855.bcm427agldvrivcd@illithid> (raw)
[-- Attachment #1: Type: text/plain, Size: 1513 bytes --]
Clean up in preparation for "MR sed".
From 0421c8301f29c2c7aeb2ebe82a72fc716617ea19 Mon Sep 17 00:00:00 2001
From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Date: Fri, 28 Jul 2023 11:52:34 -0500
Subject: [PATCH 2/6] vfork.2: ffix
* Use typographer's quotation marks.
* Quote the 4.2BSD vfork(2) page _exactly_, including font styling.
https://minnie.tuhs.org/cgi-bin/utree.pl?file=4.2BSD/usr/man/man2/vfork.2
This is to remove a false positive in preparation for a sed(1)-driven
update of man page cross references to use the groff 1.23.0 `MR` macro.
Signed-off-by: G. Branden Robinson <g.branden.robinson@gmail.com>
---
man2/vfork.2 | 9 ++++-----
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git a/man2/vfork.2 b/man2/vfork.2
index 3a65010ca..d5ea876e3 100644
--- a/man2/vfork.2
+++ b/man2/vfork.2
@@ -149,13 +149,12 @@ .SH VERSIONS
Some consider the semantics of
.BR vfork ()
to be an architectural blemish, and the 4.2BSD man page stated:
-"This system call will be eliminated when proper system sharing mechanisms
-are implemented.
+\[lq]This system call will be eliminated when proper system sharing
+mechanisms are implemented.
Users should not depend on the memory sharing semantics of
-.BR vfork ()
+.I vfork
as it will, in that case, be made synonymous to
-.BR fork (2).\c
-"
+.IR fork .\[rq]
However, even though modern memory management hardware
has decreased the performance difference between
.BR fork (2)
--
2.30.2
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2023-07-28 17:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-28 17:58 G. Branden Robinson [this message]
2023-07-28 20:58 ` [PATCH 2/6] vfork.2: ffix 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=20230728175855.bcm427agldvrivcd@illithid \
--to=g.branden.robinson@gmail.com \
--cc=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