linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
To: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: SEE ALSO: func based or man page based?
Date: Tue, 16 Feb 2016 17:26:13 -0500	[thread overview]
Message-ID: <20160216222613.GJ7732@vapier.lan> (raw)

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

i often remember the func name "sigprocmask".  but when i'm in that page,
i have a hard time remembering the exact naming for the set operators.
rather than search, i figure just checking out the SEE ALSO section will
quickly answer me ... except it doesn't (directly).

this is what sigprocmask(2) has:
SEE ALSO
    kill(2), pause(2), sigaction(2), signal(2), sigpending(2),
    sigsuspend(2), pthread_sigmask(3), sigqueue(3), sigsetops(3),
    signal(7)

i read that a few times and then just start picking signal related
pages until i stumble across sigsetops(3).

is there a policy against listing the functions that appear in a
grouped page ?  or would it be ok to add the funcs in the sigsetops
page directly to sigprocmask's SEE ALSO ?  grepping shows that at
least select_tut(2) is out of sync ...
-mike

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

             reply	other threads:[~2016-02-16 22:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-16 22:26 Mike Frysinger [this message]
     [not found] ` <20160216222613.GJ7732-UgUKS2FnFs9+urZeOPWqwQ@public.gmane.org>
2016-02-17  9:58   ` SEE ALSO: func based or man page based? Michael Kerrisk (man-pages)
     [not found]     ` <56C44463.105-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-02-17 16:28       ` Mike Frysinger
     [not found]         ` <20160217162815.GM7732-UgUKS2FnFs9+urZeOPWqwQ@public.gmane.org>
2016-02-18 11:10           ` 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=20160216222613.GJ7732@vapier.lan \
    --to=vapier-abrp7r+bbdudnm+yrofe0a@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@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).