From: Collin Funk <collin.funk1@gmail.com>
To: Alejandro Colomar <alx@kernel.org>
Cc: Collin Funk <collin.funk1@gmail.com>, linux-man@vger.kernel.org
Subject: [PATCH 2/3] man/man3/ftime.3: Declare ftime with [[deprecated]].
Date: Wed, 18 Jun 2025 21:22:10 -0700 [thread overview]
Message-ID: <5924c3b09d8e373be6ac1b5ca663b8ad7d106d93.1750306917.git.collin.funk1@gmail.com> (raw)
In-Reply-To: <c9251b002761c8c5756780432e5fccd2bc58e67b.1750306917.git.collin.funk1@gmail.com>
This function was marked as legacy in POSIX.1-2001 and has been removed
from many systems, including glibc.
Signed-off-by: Collin Funk <collin.funk1@gmail.com>
---
man/man3/ftime.3 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/man/man3/ftime.3 b/man/man3/ftime.3
index a34b15888..8ae808ec2 100644
--- a/man/man3/ftime.3
+++ b/man/man3/ftime.3
@@ -13,7 +13,7 @@ .SH SYNOPSIS
.nf
.B "#include <sys/timeb.h>"
.P
-.BI "int ftime(struct timeb *" tp );
+.BI "[[deprecated]] int ftime(struct timeb *" tp );
.fi
.SH DESCRIPTION
.BR NOTE :
--
2.49.0
next prev parent reply other threads:[~2025-06-19 4:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-19 4:22 [PATCH 1/3] man/man2/gettimeofday.2: Declare gettimeofday with [[deprecated]] Collin Funk
2025-06-19 4:22 ` Collin Funk [this message]
2025-06-23 0:45 ` [PATCH 2/3] man/man3/ftime.3: Declare ftime " Alejandro Colomar
2025-06-19 4:22 ` [PATCH 3/3] man/man3/ftime.3: Correct POSIX standards in HISTORY Collin Funk
2025-06-23 0:53 ` Alejandro Colomar
2025-06-23 2:48 ` Collin Funk
2025-06-19 11:12 ` [PATCH 1/3] man/man2/gettimeofday.2: Declare gettimeofday with [[deprecated]] Alejandro Colomar
2025-06-19 17:54 ` Collin Funk
2025-06-19 22:20 ` Alejandro Colomar
2025-06-19 22:55 ` Collin Funk
2025-06-19 22:43 ` [PATCH v2] man/man2/gettimeofday.2: Declare functions " Collin Funk
2025-06-23 0:42 ` Alejandro Colomar
2025-06-23 2:42 ` Collin Funk
2025-06-23 3:09 ` G. Branden Robinson
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=5924c3b09d8e373be6ac1b5ca663b8ad7d106d93.1750306917.git.collin.funk1@gmail.com \
--to=collin.funk1@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;
as well as URLs for NNTP newsgroup(s).