From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: ams-mXXj517/zsQ@public.gmane.org,
Jan Chaloupka <jchaloup-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
libc-alpha-9JcytcrH/bA+uJoB2kUjGw@public.gmane.org,
myllynen-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
drepper-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
pschiffe-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
Subject: Re: For review: memusage(1) man page
Date: Tue, 22 Jul 2014 08:10:18 +0200 [thread overview]
Message-ID: <53CE004A.3060706@gmail.com> (raw)
In-Reply-To: <E1X84Kh-00041J-2z-iW7gFb+/I3LZHJUXO5efmti2O/JbrIOy@public.gmane.org>
On 07/18/2014 11:20 AM, Alfred M. Szmidt wrote:
> memusage command is no documented. My collegue (95%) and I (5%)
> have written a man page for it. All informations come from
> inspecting the script code. This is the first script, others are
> memusagestat (1) and mtrace(1).
>
> This, memusagestat, and mtrace should rather be put into the glibc
> manual. mtrace is already (though partially) documented there, and
> much of the details regarding the mtrace functions. Having the
> corresponding commands documented would be awesome though.
> .
I must say that this is an odd position to take. While it would be
nice to have documentation in the glibc manual, the glibc developers
did not bother to add anything to the manual when writing these
interfaces, so it hardly seems like anyone else is obligated to do
so (assuming that person wanted to even jump the CLA hurdle...).
In any case, man pages does (good) pages that describe the
libc interfaces (including commands).
Cheers,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
--
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 prev parent reply other threads:[~2014-07-22 6:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-18 9:00 For review: memusage(1) man page Jan Chaloupka
2014-07-18 9:20 ` Alfred M. Szmidt
2014-07-18 9:50 ` Jan Chaloupka
[not found] ` <E1X84Kh-00041J-2z-iW7gFb+/I3LZHJUXO5efmti2O/JbrIOy@public.gmane.org>
2014-07-22 6:10 ` Michael Kerrisk (man-pages) [this message]
[not found] ` <53CE004A.3060706-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-07-22 8:39 ` Alfred M. Szmidt
[not found] ` <E1X9VbA-0002Bk-Ox-iW7gFb+/I3LZHJUXO5efmti2O/JbrIOy@public.gmane.org>
2014-07-22 10:20 ` Jan Chaloupka
[not found] ` <53CE3AF3.40005-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-07-22 11:00 ` Alfred M. Szmidt
[not found] ` <E1X9XoF-0007Vz-Lm-iW7gFb+/I3LZHJUXO5efmti2O/JbrIOy@public.gmane.org>
2014-07-24 5:25 ` Jan Chaloupka
2014-07-24 7:26 ` Alfred M. Szmidt
[not found] ` <E1XADPx-0007U6-2t-iW7gFb+/I3LZHJUXO5efmti2O/JbrIOy@public.gmane.org>
2014-07-24 7:39 ` Jan Chaloupka
2014-07-22 19:02 ` Michael Kerrisk (man-pages)
2014-07-23 14:41 ` Alfred M. Szmidt
[not found] ` <53C8E244.2080901-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-07-22 6:14 ` Michael Kerrisk (man-pages)
[not found] ` <53CE0144.7050405-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-07-22 6:30 ` Jan Chaloupka
[not found] ` <53CE0517.2040005-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-07-22 8:07 ` Jan Chaloupka
[not found] ` <53CE1BC4.6040707-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-08-04 5:26 ` Jan Chaloupka
2014-08-30 13:57 ` Michael Kerrisk (man-pages)
[not found] ` <5401D83C.3050806-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-09-01 7:22 ` Jan Chaloupka
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=53CE004A.3060706@gmail.com \
--to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=ams-mXXj517/zsQ@public.gmane.org \
--cc=drepper-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=jchaloup-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=libc-alpha-9JcytcrH/bA+uJoB2kUjGw@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=myllynen-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=pschiffe-H+wXaHxf7aLQT0dZR+AlfA@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.