From: Seonghun Lim <wariua-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [patch] err.3: clean up description of error message source
Date: Wed, 31 Aug 2011 23:33:24 +0900 [thread overview]
Message-ID: <4E5E4634.80609@gmail.com> (raw)
man-pages version: latest git repository
why:
In the second paragraph of DESCRIPTION section, one of the
sources of error messages is incorrect: the four functions obtain
error message only from errno, and "a code" is just relavant
with errc() and warnc(), which are not present on Linux.
see http://www.unix.com/man-page/freebsd/3/ERR/ .
Then, the third paragraph becomes a duplicate.
diff --git a/man3/err.3 b/man3/err.3
--- a/man3/err.3
+++ b/man3/err.3
@@ -83,7 +83,7 @@ and
.BR vwarn ()
functions append an error message obtained from
.BR strerror (3)
-based on a code or the global variable
+based on the global variable
.IR errno ,
preceded by another colon and space unless the
.I fmt
@@ -91,16 +91,6 @@ argument is
NULL.
.PP
The
-.BR err (),
-.BR verr (),
-.BR warn (),
-and
-.BR vwarn ()
-functions use the global variable
-.I errno
-to look up the error message.
-.PP
-The
.BR errx ()
and
.BR warnx ()
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2011-08-31 14:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-31 14:33 Seonghun Lim [this message]
[not found] ` <4E5E4634.80609-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-09-17 5:15 ` [patch] err.3: clean up description of error message source Michael Kerrisk
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=4E5E4634.80609@gmail.com \
--to=wariua-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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