All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org>
To: Aurelien Aptel <aaptel-IBi9RG/b67k@public.gmane.org>,
	linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Subject: Re: [PATCH v2] man: generate all man pages from POD files when buidling
Date: Fri, 06 Oct 2017 06:37:44 -0400	[thread overview]
Message-ID: <1507286264.5438.0.camel@samba.org> (raw)
In-Reply-To: <20170929140303.24880-1-aaptel-IBi9RG/b67k@public.gmane.org>

On Fri, 2017-09-29 at 16:03 +0200, Aurelien Aptel wrote:
> Move all man pages to easily editable POD files and generate troff
> source when building.
> 
> Previous .in troff file are still preprocessed before final generation
> to use configured path (.pod.in -> .pod -> troff). All temporary
> files (.pod.in and troff sources) are properly deleted on clean.
> 
> Remove all troff file, no need to keep generated copies under source
> control.
> 
> This commit does not change the content of the man pages but makes
> future editing easier.
> 
> Adds a new --enable-man/--disable-man configure option to control the
> generation and installation of man pages. The option is automatically
> enabled if the system supports it. Explicitely enabling it will make the
> configure script fail if pod2man is not installed.
> 
> Signed-off-by: Aurelien Aptel <aaptel-IBi9RG/b67k@public.gmane.org>
> ---
> 
> changes in v2:
> 
> * add the configure flag for man page generation
> * check/autodetect if pod2man is available
> 
>  Makefile.am                   |  88 ++--
>  cifs.idmap.8.in               | 101 -----
>  cifs.idmap.pod.in             | 100 +++++
>  cifs.upcall.8.in              | 132 ------
>  cifs.upcall.pod.in            | 147 +++++++
>  cifscreds.1                   | 200 ---------
>  configure.ac                  |  21 +
>  getcifsacl.1.in               |  59 ---
>  getcifsacl.pod.in             |  60 +++
>  idmapwb.8.in                  | 148 -------
>  idmapwb.pod => idmapwb.pod.in |   0
>  mount.cifs.8                  | 856 --------------------------------------
>  mount.cifs.pod                | 933 ++++++++++++++++++++++++++++++++++++++++++
>  pam_cifscreds.8               | 207 ----------
>  pam_cifscreds.pod             |   2 +-
>  setcifsacl.1.in               | 113 -----
>  setcifsacl.pod.in             | 117 ++++++
>  17 files changed, 1431 insertions(+), 1853 deletions(-)
>  delete mode 100644 cifs.idmap.8.in
>  create mode 100644 cifs.idmap.pod.in
>  delete mode 100644 cifs.upcall.8.in
>  create mode 100644 cifs.upcall.pod.in
>  delete mode 100644 cifscreds.1
>  delete mode 100644 getcifsacl.1.in
>  create mode 100644 getcifsacl.pod.in
>  delete mode 100644 idmapwb.8.in
>  rename idmapwb.pod => idmapwb.pod.in (100%)
>  delete mode 100644 mount.cifs.8
>  create mode 100644 mount.cifs.pod
>  delete mode 100644 pam_cifscreds.8
>  delete mode 100644 setcifsacl.1.in
>  create mode 100644 setcifsacl.pod.in

Merged.
-- 
Jeff Layton <jlayton-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org>

  parent reply	other threads:[~2017-10-06 10:37 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     ` Jeff Layton [this message]
2017-10-23 12:31     ` [PATCH v2] " Jeff Layton
     [not found]       ` <1508761900.5859.10.camel-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org>
2017-10-23 14:23         ` Aurélien Aptel

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=1507286264.5438.0.camel@samba.org \
    --to=jlayton-eunubhrolfbytjvyw6ydsg@public.gmane.org \
    --cc=aaptel-IBi9RG/b67k@public.gmane.org \
    --cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@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.