From: Mike Frysinger <vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
To: Xose Vazquez Perez
<xose.vazquez-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: How to find bugs in man pages?
Date: Mon, 20 Jun 2016 16:45:56 -0400 [thread overview]
Message-ID: <20160620204556.GP24532@vapier.lan> (raw)
In-Reply-To: <49d6a2b1-0069-9325-08a1-c7e48205a787-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 146 bytes --]
On 19 Jun 2016 16:46, Xose Vazquez Perez wrote:
> I'm using: groff -z -b -wall manpage.x
seems like something we could add to `make check`
-mike
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-06-20 20:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-19 14:46 How to find bugs in man pages? Xose Vazquez Perez
[not found] ` <49d6a2b1-0069-9325-08a1-c7e48205a787-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-06-20 20:45 ` Mike Frysinger [this message]
[not found] ` <20160620204556.GP24532-UgUKS2FnFs9+urZeOPWqwQ@public.gmane.org>
2016-08-08 19:38 ` Michael Kerrisk (man-pages)
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=20160620204556.GP24532@vapier.lan \
--to=vapier-abrp7r+bbdudnm+yrofe0a@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=xose.vazquez-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 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).