From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: David Herrmann <dh.herrmann@googlemail.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH libdrm 1/4] man: use automake man_MANS to allow multiple suffixes
Date: Thu, 27 Sep 2012 09:24:44 -0700 [thread overview]
Message-ID: <20120927092444.7dd8ee0b@jbarnes-desktop> (raw)
In-Reply-To: <1348411208-3943-2-git-send-email-dh.herrmann@googlemail.com>
On Sun, 23 Sep 2012 16:40:04 +0200
David Herrmann <dh.herrmann@googlemail.com> wrote:
> Current man-page infrastructure supports only man3 but we wanto overview
> files to be placed in man7. So use the new automake support for man_MANS
> which installs the files automatically in the right location.
>
> The current man-pages are simply moved and their header line is adjusted to the
> new man-page headers.
>
> Signed-off-by: David Herrmann <dh.herrmann@googlemail.com>
> ---
Yeah looks nice.
Reviewed-by: Jesse Barnes <jbarnes@virtuousgeek.org>
--
Jesse Barnes, Intel Open Source Technology Center
next prev parent reply other threads:[~2012-09-27 16:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-23 14:40 [PATCH libdrm 0/4] Overview man-pages for libdrm David Herrmann
2012-09-23 14:40 ` [PATCH libdrm 1/4] man: use automake man_MANS to allow multiple suffixes David Herrmann
2012-09-27 16:24 ` Jesse Barnes [this message]
2012-09-23 14:40 ` [PATCH libdrm 2/4] man: add man/drm.7 overview page David Herrmann
2012-09-27 16:25 ` Jesse Barnes
2012-09-23 14:40 ` [PATCH libdrm 3/4] man: add KMS " David Herrmann
2012-09-27 16:28 ` Jesse Barnes
2012-09-23 14:40 ` [PATCH libdrm 4/4] man: add drm-memory man-page David Herrmann
2012-09-24 7:45 ` Michel Dänzer
2012-09-24 16:58 ` David Herrmann
2012-09-27 16:31 ` Jesse Barnes
2012-09-24 19:51 ` [PATCH libdrm 0/4] Overview man-pages for libdrm Thierry Reding
2012-09-24 21:35 ` David Herrmann
2012-09-24 21:41 ` Alan Coopersmith
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=20120927092444.7dd8ee0b@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=dh.herrmann@googlemail.com \
--cc=dri-devel@lists.freedesktop.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.