From: "Carlos O'Donell" <carlos-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Michael Kerrisk
<mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
"linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: [patch 1/7] getgrent_r.3: wfix
Date: Thu, 15 Jan 2015 22:18:16 -0500 [thread overview]
Message-ID: <54B882F8.3080203@redhat.com> (raw)
Harmonize all the manual pages to use "stream" for FILE*
instead of randomly using "fp" or "stream." Choosing something
and being consistent helps users scan the man pages quickly
and understand what they are looking at.
Patch against master.
diff --git a/man3/getgrent_r.3 b/man3/getgrent_r.3
index 8f33851..6e1078d 100644
--- a/man3/getgrent_r.3
+++ b/man3/getgrent_r.3
@@ -32,7 +32,7 @@ getgrent_r, fgetgrent_r \- get group file entry reentrantly
.br
.BI " size_t " buflen ", struct group **" gbufp );
.sp
-.BI "int fgetgrent_r(FILE *" fp ", struct group *" gbuf ", char *" buf ,
+.BI "int fgetgrent_r(FILE *" stream ", struct group *" gbuf ", char *" buf ,
.br
.BI " size_t " buflen ", struct group **" gbufp );
.fi
@@ -59,8 +59,8 @@ and
.BR fgetgrent (3).
The former reads the next group entry from the stream initialized by
.BR setgrent (3).
-The latter reads the next group entry from the stream
-.IR fp .
+The latter reads the next group entry from the
+.IR stream .
.PP
The \fIgroup\fP structure is defined in
.I <grp.h>
---
Cheers,
Carlos.
--
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:[~2015-01-16 3:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-16 3:18 Carlos O'Donell [this message]
[not found] ` <54B882F8.3080203-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-01-16 5:59 ` [patch 1/7] getgrent_r.3: wfix Michael Kerrisk (man-pages)
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=54B882F8.3080203@redhat.com \
--to=carlos-h+wxahxf7alqt0dzr+alfa@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;
as well as URLs for NNTP newsgroup(s).