linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Helge Kreutzmann <debian@helgefjell.de>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: linux-man@vger.kernel.org
Subject: Re: Errors in man pages, here: getgrent(3): Understanding
Date: Fri, 1 May 2020 09:13:39 +0200	[thread overview]
Message-ID: <20200501071339.GB938@Debian-50-lenny-64-minimal> (raw)
In-Reply-To: <e4a94746-86b5-de7c-73cb-3c939910a404@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1054 bytes --]

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".

Thanks.

Greetings

          Helge
-- 
      Dr. Helge Kreutzmann                     debian@helgefjell.de
           Dipl.-Phys.                   http://www.helgefjell.de/debian.php
        64bit GNU powered                     gpg signed mail preferred
           Help keep free software "libre": http://www.ffii.de/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2020-05-01  7:13 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 [this message]
2020-05-01  8:29     ` 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=20200501071339.GB938@Debian-50-lenny-64-minimal \
    --to=debian@helgefjell.de \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    /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).