From: Jan Chaloupka <jchaloup-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Mike Frysinger <vapier-aBrp7R+bbdUdnm+yROfE0A@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,
Peter Schiffer <pschiffe-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Subject: Re: For review: mtrace(1) man page
Date: Mon, 04 Aug 2014 07:24:57 +0200 [thread overview]
Message-ID: <53DF1929.3050207@redhat.com> (raw)
In-Reply-To: <1777637.kUP8sTC8nC@vapier>
Hi, Mike
On 08/02/2014 06:57 PM, 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.
First thing I do, when I need help, is to look into man page. Why? it is
fast.
> 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.
I have nothing againts putting it into glibc itself as well.
> how else do people feel in this regard ?
> -mike
Jan
--
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-08-04 5:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-18 9:01 For review: mtrace(1) man page Jan Chaloupka
[not found] ` <CABQpAL4JoZw8VqPNTuxnF2Nk+-zrt8srkzmxtYgi0XK9tC+9cQ@mail.gmail.com>
[not found] ` <CABQpAL4JoZw8VqPNTuxnF2Nk+-zrt8srkzmxtYgi0XK9tC+9cQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-07-22 8:17 ` Jan Chaloupka
[not found] ` <53CE1E27.5020400-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-08-30 13:34 ` Michael Kerrisk (man-pages)
[not found] ` <53C8E24E.3040704-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-08-02 16:57 ` Mike Frysinger
2014-08-04 5:24 ` Jan Chaloupka [this message]
2014-08-22 23:07 ` Michael Kerrisk (man-pages)
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=53DF1929.3050207@redhat.com \
--to=jchaloup-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=drepper-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=libc-alpha-9JcytcrH/bA+uJoB2kUjGw@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=myllynen-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=pschiffe-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=vapier-aBrp7R+bbdUdnm+yROfE0A@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.