This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: For review: mtrace(1) man page

From: Mike Frysinger <vapier at gentoo dot org>
To: 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: Sat, 02 Aug 2014 12:57:18 -0400
Subject: Re: For review: mtrace(1) man page
Authentication-results: sourceware.org; auth=none
References: <53C8E24E dot 3040704 at redhat dot com>

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.

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

Attachment: signature.asc
Description: This is a digitally signed message part.

Follow-Ups:
- Re: For review: mtrace(1) man page
  - From: Jan Chaloupka
- Re: For review: mtrace(1) man page
  - From: Michael Kerrisk (man-pages)

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]