From: Colin Watson <cjwatson-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.org>
To: Michael Kerrisk <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: gethostid/sethostid in wrong manual section
Date: Mon, 22 Dec 2008 23:39:53 +0000 [thread overview]
Message-ID: <20081222233953.GG16155@riva.ucam.org> (raw)
https://bugs.launchpad.net/ubuntu/+source/manpages/+bug/17551 reports
(and I've confirmed) that gethostid/sethostid are in section 2 despite
being implemented by glibc, not the kernel; they aren't just syscall
stubs either. Should they be moved to section 3?
Thanks,
--
Colin Watson [cjwatson-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.org]
--
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:[~2008-12-22 23:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-22 23:39 Colin Watson [this message]
[not found] ` <20081222233953.GG16155-K2jUmMR1UYV4cg9Nei1l7Q@public.gmane.org>
2009-01-12 18:46 ` gethostid/sethostid in wrong manual section 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=20081222233953.GG16155@riva.ucam.org \
--to=cjwatson-gewih/nmzzlqt0dzr+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