From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Helge Kreutzmann <debian@helgefjell.de>
Cc: linux-man <linux-man@vger.kernel.org>
Subject: Re: Errors in man pages, here: getgrent(3): Understanding
Date: Fri, 1 May 2020 10:29:39 +0200 [thread overview]
Message-ID: <CAKgNAkiASdoFzApSyGNUP4hG+=WSTe8mGJzNfgFkuj8Zg2MtsA@mail.gmail.com> (raw)
In-Reply-To: <20200501071339.GB938@Debian-50-lenny-64-minimal>
On Fri, 1 May 2020 at 09:13, Helge Kreutzmann <debian@helgefjell.de> wrote:
>
> Hello Michael,
> On Mon, Apr 20, 2020 at 11:54:57AM +0200, Michael Kerrisk (man-pages) wrote:
> > On 4/19/20 8:48 AM, Helge Kreutzmann wrote:
> > > explain|reword "broken-out" or skip it
> > >
> > > "The B<getgrent>() function returns a pointer to a structure containing the "
> > > "broken-out fields of a record in the group database (e.g., the local group "
> > > "file I</etc/group>, NIS, and LDAP). The first time B<getgrent>() is "
> > > "called, it returns the first entry; thereafter, it returns successive "
> > > "entries."
> >
> > I don't really see what the problem is. "broken-out" seems
> > reasonably clear to me. I'm ignoring this for now.
>
> I then assume that it is a synonym for "extracted" or "taken out".
Yes. The fields are "broken out" from the "complete" record in the database.
Thanks,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
prev parent reply other threads:[~2020-05-01 8:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-19 6:48 Errors in man pages, here: getgrent(3): Understanding Helge Kreutzmann
2020-04-20 9:54 ` Michael Kerrisk (man-pages)
2020-05-01 7:13 ` Helge Kreutzmann
2020-05-01 8:29 ` Michael Kerrisk (man-pages) [this message]
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='CAKgNAkiASdoFzApSyGNUP4hG+=WSTe8mGJzNfgFkuj8Zg2MtsA@mail.gmail.com' \
--to=mtk.manpages@gmail.com \
--cc=debian@helgefjell.de \
--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).