From: Samanta Navarro <ferivoz@riseup.net>
To: alx@kernel.org
Cc: linux-man@vger.kernel.org
Subject: [patch] printf.h.3head: tfix
Date: Thu, 14 Mar 2024 12:21:50 +0000 [thread overview]
Message-ID: <lor74cubqig2xpdblvkxgyh6chwveyrdepgydtxfrpo6psmgrg@hqlvktvd7yqa> (raw)
diff --git a/man3head/printf.h.3head b/man3head/printf.h.3head
index a5c7d1c..8f647af 100644
--- a/man3head/printf.h.3head
+++ b/man3head/printf.h.3head
@@ -231,7 +231,7 @@ and is now deprecated.
That function can't handle user-defined types.
.P
.BR \%register_printf_specifier ()
-superseeds
+supersedes
.BR \%register_printf_function (3).
.SH EXAMPLES
The following example program registers the 'b' and 'B' specifiers
next reply other threads:[~2024-03-14 12:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-14 12:21 Samanta Navarro [this message]
2024-03-14 16:38 ` [patch] printf.h.3head: tfix 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=lor74cubqig2xpdblvkxgyh6chwveyrdepgydtxfrpo6psmgrg@hqlvktvd7yqa \
--to=ferivoz@riseup.net \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).