From: bugme-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r@public.gmane.org
To: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [Bug 11060] New: man2/getrusage.2 does not explain RUSAGE_THREAD
Date: Wed, 9 Jul 2008 02:14:53 -0700 (PDT) [thread overview]
Message-ID: <bug-11060-11311@http.bugzilla.kernel.org/> (raw)
http://bugzilla.kernel.org/show_bug.cgi?id=11060
Summary: man2/getrusage.2 does not explain RUSAGE_THREAD
Product: Documentation
Version: unspecified
KernelVersion: v2.6.25-6070-g679c9cd
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: man-pages
AssignedTo: documentation_man-pages-ztI5WcYan/vQLgFONoPN62D2FQJk+8+b@public.gmane.org
ReportedBy: knikanth-l3A5Bk7waGM@public.gmane.org
CC: sripathik-xthvdsQ13ZrQT0dZR+AlfA@public.gmane.org, roland-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
commit 679c9cd4acc2cf2872171813752eab3320273339 v2.6.25-6070-g679c9cd adds
RUSAGE_THREAD option to getrusage which is not documented in man pages
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
--
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-07-09 9:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-09 9:14 bugme-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r [this message]
[not found] ` <bug-11060-11311-V0hAGp6uBxO456/isadD/XN4h3HLQggn@public.gmane.org/>
2008-07-09 9:48 ` [Bug 11060] man2/getrusage.2 does not explain RUSAGE_THREAD bugme-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r
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=bug-11060-11311@http.bugzilla.kernel.org/ \
--to=bugme-daemon-590eeb7gvniway/ihj7yzeb+6bgklq7r@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.