From: Kristaps Dzonsons <kristaps@bsd.lv>
To: discuss@mdocml.bsd.lv
Cc: Abhinav Upadhyay <er.abhinav.upadhyay@gmail.com>
Subject: Re: Bug in the mandoc(3) man page
Date: Tue, 18 Oct 2011 15:25:43 +0200 [thread overview]
Message-ID: <4E9D7E57.90005@bsd.lv> (raw)
In-Reply-To: <CAHwRYJ=2dBM4Y2V7R4t1wF2drhHrx7uvvV=-4xiGaj4hpwBX-A@mail.gmail.com>
On 10/18/11 15:02, Abhinav Upadhyay wrote:
> Hello,
>
> I think there is some inconsistency in the mandoc(3) man page. The
> argument names of mandoc_escape function in the SYNOPSIS section do
> not agree with the argument names in the DESCRIPTION section. I
> referred to the source file and corrected the argument names in
> SYNOPSIS. Following is the diff (taken against mdocml 1.12 in NetBSD
> -current), if you think it is ok, then please
> fix this :)
Abhinav,
Thanks for the report---fixed!
Take care,
Kristaps
--
To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv
prev parent reply other threads:[~2011-10-18 13:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHwRYJ=STvxAt4PWoJOMzHpGQuNGKtyUUwHV9AWVm0mBV+tp6Q@mail.gmail.com>
2011-10-18 13:02 ` Abhinav Upadhyay
2011-10-18 13:25 ` Kristaps Dzonsons [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=4E9D7E57.90005@bsd.lv \
--to=kristaps@bsd.lv \
--cc=discuss@mdocml.bsd.lv \
--cc=er.abhinav.upadhyay@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).