From: "Aníbal Monsalve Salazar" <anibal@debian.org>
To: linux-nfs@vger.kernel.org
Subject: [PATCH] nfsidmap: idmapd.conf.5 man warnings
Date: Sat, 25 May 2013 12:12:48 +1000 [thread overview]
Message-ID: <20130525021248.GA10636@master.debian.org> (raw)
I'm using the patch in this message to build libnfsidmap in Debian.
The following command:
MANROFFSEQ='' MANWIDTH=80 man --warnings -l -Z ./idmapd.conf.5 >/dev/null
shows the following warnings:
<standard input>:237: warning: macro `"' not defined
<standard input>:269: warning: macro `fo' not defined
<standard input>:278: warning: macro `".SH' not defined
and the patch below fixes them.
--- a/idmapd.conf.5 2011-12-06 07:28:10.000000000 +1100
+++ b/idmapd.conf.5 2013-05-25 11:07:37.000000000 +1000
@@ -31,7 +31,7 @@
.\"
.TH idmapd.conf 5 "19 Nov 2008"
.SH NAME
-idmapd.conf
+idmapd.conf \- configuration file for libnfsidmap
.SH SYNOPSIS
Configuration file for libnfsidmap. Used by idmapd and svcgssd to map NFSv4 name to and from ids.
.SH DESCRIPTION
@@ -234,7 +234,6 @@ Number of seconds before timing out an L
.\" -------------------------------------------------------------------
.\"
.SH EXAMPLES
-."
An example
.I /etc/idmapd.conf
file:
@@ -266,7 +265,6 @@ johndoe@OTHER.DOMAIN.ORG = johnny
LDAP_server = ldap.domain.org
LDAP_base = dc=org,dc=domain
-.fo
.\"
.\" -------------------------------------------------------------------
.\" Additional sections
@@ -275,11 +273,11 @@ LDAP_base = dc=org,dc=domain
.SH SEE ALSO
.BR idmapd (8)
.BR svcgssd (8)
-.".SH COMPATIBILITY
-.".SH STANDARDS
-.".SH ACKNOWLEDGEMENTS
-.".SH AUTHORS
-.".SH HISTORY
+.\".SH COMPATIBILITY
+.\".SH STANDARDS
+.\".SH ACKNOWLEDGEMENTS
+.\".SH AUTHORS
+.\".SH HISTORY
.SH BUGS
Report bugs to <nfsv4@linux-nfs.org>
-.".SH CAVEATS
+.\".SH CAVEATS
next reply other threads:[~2013-05-25 2:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-25 2:12 Aníbal Monsalve Salazar [this message]
2013-05-28 17:53 ` [PATCH] nfsidmap: idmapd.conf.5 man warnings Steve Dickson
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=20130525021248.GA10636@master.debian.org \
--to=anibal@debian.org \
--cc=linux-nfs@vger.kernel.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.