Skip to contentSkip to conversation

vfork.2: ffix

PATCH In review G. Branden Robinson 2 participants 2 messages Jul 28, 2023 Man-pages: manual pages for Linux -- Sections 2, 3, 4, 5, and 7

lore
Share & tools
lore

G. Branden Robinson

author
#0 lore raw

PATCH 2/6 vfork.2: ffix

Clean up in preparation for "MR sed".

From 0421c8301f29c2c7aeb2ebe82a72fc716617ea19 Mon Sep 17 00:00:00 2001
From: "G. Branden Robinson" <[email protected]>
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 <[email protected]>
---
 man2/vfork.2 | 9 ++++-----
 1 file changed, 4 insertions(+), 5 deletions(-)
man2/vfork.2 +4 -5
index 3a65010ca..d5ea876e3 100644
@@ -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)
Signature · 1 line
2.30.2
maintainer
#1 lore raw
Quoted 25 lines · G. Branden Robinson

Clean up in preparation for "MR sed".

From 0421c8301f29c2c7aeb2ebe82a72fc716617ea19 Mon Sep 17 00:00:00 2001
From: "G. Branden Robinson" <[email protected]>
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 <[email protected]>
---
 man2/vfork.2 | 9 ++++-----
 1 file changed, 4 insertions(+), 5 deletions(-)
man2/vfork.2 +0 -0
index 3a65010ca..d5ea876e3 100644

man2/vfork.2 .SH VERSIONS · line 153

Quoted 7 lines
man2/vfork.2 +2 -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.

Error: write poems, not prose.

I've amended that ;-)

<https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/commit/?id=47b6b10ec8a61dade7f50d6ec2a2ff7001fb19af>

Cheers,
Alex

Quoted 10 lines
man2/vfork.2 +2 -3
 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)
Signature · 2 lines
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5