Merging upstream version 4.23.0.

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>

1 files changed, 8 insertions, 9 deletions

diff --git a/upstream/opensuse-tumbleweed/man3/bsd_signal.3 b/upstream/opensuse-tumbleweed/man3/bsd_signal.3
index 3294c5cc..183ab2eb 100644
--- a/upstream/opensuse-tumbleweed/man3/bsd_signal.3
+++ b/upstream/opensuse-tumbleweed/man3/bsd_signal.3
@@ -3,7 +3,7 @@
 .\"
 .\" SPDX-License-Identifier: Linux-man-pages-copyleft
 .\"
-.TH bsd_signal 3 2023-07-20 "Linux man-pages 6.05.01"
+.TH bsd_signal 3 2024-05-02 "Linux man-pages (unreleased)"
 .SH NAME
 bsd_signal \- signal handling with BSD semantics
 .SH LIBRARY
@@ -12,17 +12,17 @@ Standard C library
 .SH SYNOPSIS
 .nf
 .B #include <signal.h>
-.PP
+.P
 .B typedef void (*sighandler_t)(int);
-.PP
+.P
 .BI "sighandler_t bsd_signal(int " signum ", sighandler_t " handler );
 .fi
-.PP
+.P
 .RS -4
 Feature Test Macro Requirements for glibc (see
 .BR feature_test_macros (7)):
 .RE
-.PP
+.P
 .BR bsd_signal ():
 .nf
     Since glibc 2.26:
@@ -37,7 +37,7 @@ The
 .BR bsd_signal ()
 function takes the same arguments, and performs the same task, as
 .BR signal (2).
-.PP
+.P
 The difference between the two is that
 .BR bsd_signal ()
 is guaranteed to provide reliable signal semantics, that is:
@@ -73,14 +73,13 @@ T{
 .BR bsd_signal ()
 T}	Thread safety	MT-Safe
 .TE
-.sp 1
 .SH VERSIONS
 Use of
 .BR bsd_signal ()
 should be avoided; use
 .BR sigaction (2)
 instead.
-.PP
+.P
 On modern Linux systems,
 .BR bsd_signal ()
 and
@@ -91,7 +90,7 @@ But on older systems,
 provided unreliable signal semantics; see
 .BR signal (2)
 for details.
-.PP
+.P
 The use of
 .I sighandler_t
 is a GNU extension;