This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: For review: mtrace(1) man page
- From: "Michael Kerrisk (man-pages)" <mtk dot manpages at gmail dot com>
- To: Mike Frysinger <vapier at gentoo dot org>, Jan Chaloupka <jchaloup at redhat dot com>
- Cc: mtk dot manpages at gmail dot com, linux-man at vger dot kernel dot org, libc-alpha at sourceware dot org, myllynen at redhat dot com, drepper at gmail dot com, Peter Schiffer <pschiffe at redhat dot com>
- Date: Fri, 22 Aug 2014 18:07:28 -0500
- Subject: Re: For review: mtrace(1) man page
- Authentication-results: sourceware.org; auth=none
- References: <53C8E24E dot 3040704 at redhat dot com> <1777637 dot kUP8sTC8nC at vapier>
On 08/02/2014 11:57 AM, Mike Frysinger wrote:
> On Fri 18 Jul 2014 11:01:02 Jan Chaloupka wrote:
>> mtrace(1) command is not documented. All informations come from the script.
>>
>> Feel free to comment or ask any question.
>
> it doesn't feel right for truly glibc-specific tools to have their man pages
> hosted in the Linux man-pages project, especially when you consider
> functionality/flags/etc... skew across glibc versions trying to be tracked in
> an unrelated git repo.
Well, from a man-pages perspective, this doesn't seem terribly different from
the Section 3 APIs. Also, a number of glibc commands are already (in many cases,
since long ago) documented in man1 and man8.
Cheers,
Michael
> the GNU standard doesn't say that we can't include them in GNU projects, just
> that they should be secondary to info pages. so i think things like mtrace(1)
> are better in glibc itself.
>
> how else do people feel in this regard ?
> -mike
>
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/