From: Simon Essien <champbreed1@gmail.com>
To: alx@kernel.org
Cc: linux-man@vger.kernel.org, champbreed1@gmail.com
Subject: [PATCH] man3/creal.3, man3/cimag.3: Standardize style and history
Date: Tue, 6 Jan 2026 11:04:25 +0000 [thread overview]
Message-ID: <20260106110425.61812-1-champbreed1@gmail.com> (raw)
Consolidated VERSIONS and HISTORY sections to match project standards.
Moved GNU extension notes for __real__ and __imag__ to a clearer
format within VERSIONS.
Signed-off-by: Simon Essien <champbreed1@gmail.com>
---
man/man3/cimag.3 | 11 ++++-------
man/man3/creal.3 | 11 ++++-------
2 files changed, 8 insertions(+), 14 deletions(-)
diff --git a/man/man3/cimag.3 b/man/man3/cimag.3
index 39eeb1007..946e095a8 100644
--- a/man/man3/cimag.3
+++ b/man/man3/cimag.3
@@ -45,14 +45,11 @@ T{
T} Thread safety MT-Safe
.TE
.SH VERSIONS
-GCC also supports __imag__.
-That is a GNU extension.
+Available since glibc 2.1.
+GCC also supports the
+.BR __real__
+keyword (a GNU extension).
.SH STANDARDS
C11, POSIX.1-2008.
.SH HISTORY
-glibc 2.1.
C99, POSIX.1-2001.
-.SH SEE ALSO
-.BR cabs (3),
-.BR creal (3),
-.BR complex (7)
diff --git a/man/man3/creal.3 b/man/man3/creal.3
index be07d8273..d05125274 100644
--- a/man/man3/creal.3
+++ b/man/man3/creal.3
@@ -43,14 +43,11 @@ T{
T} Thread safety MT-Safe
.TE
.SH VERSIONS
-GCC supports also __real__.
-That is a GNU extension.
+Available since glibc 2.1.
+GCC also supports the
+.BR __real__
+keyword (a GNU extension).
.SH STANDARDS
C11, POSIX.1-2008.
.SH HISTORY
-glibc 2.1.
C99, POSIX.1-2001.
-.SH SEE ALSO
-.BR cabs (3),
-.BR cimag (3),
-.BR complex (7)
--
2.51.0
next reply other threads:[~2026-01-06 11:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-06 11:04 Simon Essien [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-01-06 10:53 [PATCH] man3/creal.3, man3/cimag.3: Standardize style and history Simon Essien
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=20260106110425.61812-1-champbreed1@gmail.com \
--to=champbreed1@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