From: "Aurélien Aptel" <aaptel-IBi9RG/b67k@public.gmane.org>
To: Jeff Layton <jlayton-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org>
Cc: smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
Pavel Shilovskiy
<pshilov-0li6OtcxBFHby3iVrkZq2A@public.gmane.org>,
linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH v2] man: generate all man pages from POD files when buidling
Date: Mon, 23 Oct 2017 16:23:02 +0200 [thread overview]
Message-ID: <mps8tg2t03d.fsf@aaptelpc.suse.de> (raw)
In-Reply-To: <1508761900.5859.10.camel-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org>
Jeff Layton <jlayton-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org> writes:
> A one time conversion to rst files and twiddle the Makefile.am to use
> rst2man and I think we'd be done. I'm happy to do the work, but I wanted
> to run it by you in case you had a particular attachment to pod files.
I've just picked POD because there was already POD files in the
tree. You can go ahead if you prefer RST, I personally don't mind much
as long as it's not troff :)
Cheers,
--
Aurélien Aptel / SUSE Labs Samba Team
GPG: 1839 CB5F 9F5B FB9B AA97 8C99 03C8 A49B 521B D5D3
SUSE Linux GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
prev parent reply other threads:[~2017-10-23 14:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170920222053.7977-1-aaptel@suse.com>
[not found] ` <1506431475.3182.4.camel@samba.org>
[not found] ` <1506431475.3182.4.camel-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org>
2017-09-26 14:50 ` [PATCH] man: generate all man pages from POD files when buidling Aurélien Aptel
[not found] ` <20170929140303.24880-1-aaptel@suse.com>
[not found] ` <20170929140303.24880-1-aaptel-IBi9RG/b67k@public.gmane.org>
2017-10-06 10:37 ` [PATCH v2] " Jeff Layton
2017-10-23 12:31 ` Jeff Layton
[not found] ` <1508761900.5859.10.camel-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org>
2017-10-23 14:23 ` Aurélien Aptel [this message]
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=mps8tg2t03d.fsf@aaptelpc.suse.de \
--to=aaptel-ibi9rg/b67k@public.gmane.org \
--cc=jlayton-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=pshilov-0li6OtcxBFHby3iVrkZq2A@public.gmane.org \
--cc=smfrench-Re5JQEeQqe8AvxtiuMwx3w@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.