From: Ingo Schwarze <schwarze@usta.de>
To: Thomas Klausner <wiz@NetBSD.org>
Cc: tech@mdocml.bsd.lv, Joerg Sonnenberger <joerg@britannica.bec.de>
Subject: Re: call for testing: mandoc-1.13.4 release candidate
Date: Sat, 9 Jul 2016 17:30:18 +0200 [thread overview]
Message-ID: <20160709153018.GC6629@athene.usta.de> (raw)
In-Reply-To: <20160709131828.GB5161@danbala.tuwien.ac.at>
Hi Thomas & Joerg,
Thomas Klausner NetBSD wrote on Sat, Jul 09, 2016 at 03:18:28PM +0200:
> I've tested 1.13.4rc1 on NetBSD-7.99.33 and it built fine, thank you.
Thank you!
> There are a couple of patches in pkgsrc by joerg that, it seems, have
> not been sent upstream. They remove the inclusion of getopt.h. At
> least on NetBSD, the getopt(3) man page mentions that getopt is in
> unistd.h.
OpenBSD manuals and header files agree, and more importantly,
so does POSIX. Nothing break on Linux, Solaris 9, 10, or 11
either, so i committed the patch.
Thank you,
Ingo
> $NetBSD: patch-demandoc.c,v 1.1 2015/12/10 02:50:19 joerg Exp $
>
> --- demandoc.c.orig 2015-12-07 15:20:07.413956576 +0000
> +++ demandoc.c
> @@ -20,7 +20,6 @@
>
> #include <assert.h>
> #include <ctype.h>
> -#include <getopt.h>
> #include <stdio.h>
> #include <stdlib.h>
> #include <string.h>
> $NetBSD: patch-mandocdb.c,v 1.7 2015/12/10 02:50:19 joerg Exp $
>
> --- mandocdb.c.orig 2015-12-07 15:20:09.513956486 +0000
> +++ mandocdb.c
> @@ -30,7 +30,6 @@
> #else
> #include "compat_fts.h"
> #endif
> -#include <getopt.h>
> #include <limits.h>
> #include <stddef.h>
> #include <stdio.h>
> $NetBSD: patch-manpage.c,v 1.1 2015/12/10 02:50:19 joerg Exp $
>
> --- manpage.c.orig 2015-12-07 15:20:30.565955584 +0000
> +++ manpage.c
> @@ -20,7 +20,6 @@
> #include <sys/types.h>
>
> #include <assert.h>
> -#include <getopt.h>
> #include <limits.h>
> #include <stdint.h>
> #include <stdio.h>
> $NetBSD: patch-mansearch.c,v 1.1 2015/12/10 02:50:19 joerg Exp $
>
> --- mansearch.c.orig 2016-07-09 11:15:54.000000000 +0000
> +++ mansearch.c
> @@ -26,7 +26,6 @@
> #endif
> #include <errno.h>
> #include <fcntl.h>
> -#include <getopt.h>
> #include <glob.h>
> #include <limits.h>
> #include <regex.h>
--
To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv
next prev parent reply other threads:[~2016-07-09 15:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <sfid-H20160709-151232-+015.17-1@spamfilter.osbf.lua>
[not found] ` <20160709131158.GA6629@athene.usta.de>
2016-07-09 13:18 ` Thomas Klausner
2016-07-09 15:30 ` Ingo Schwarze [this message]
2016-07-09 13:39 ` Baptiste Daroussin FreeBSD
2016-07-09 14:31 ` Anthony J. Bentley
2016-07-09 15:29 ` New db format (was Re: call for testing: mandoc-1.13.4 release candidate) Baptiste Daroussin
2016-07-09 16:12 ` New db format Ingo Schwarze
2016-08-05 20:26 ` Baptiste Daroussin
2016-07-09 14:28 ` call for testing: mandoc-1.13.4 release candidate Svyatoslav Mishyn Crux
2016-07-10 14:08 ` Ingo Schwarze
2016-07-09 18:21 ` Svyatoslav Mishyn
2016-07-09 21:13 ` Ingo Schwarze
2016-07-09 18:55 ` Svyatoslav Mishyn Crux
2016-07-10 10:46 ` Svyatoslav Mishyn
2016-07-10 13:39 ` Ingo Schwarze
2016-07-10 14:27 ` Christian Neukirchen
2016-07-10 16:36 ` Ingo Schwarze
2016-07-10 16:48 ` Christian Neukirchen
2016-07-10 18:34 ` Ingo Schwarze
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=20160709153018.GC6629@athene.usta.de \
--to=schwarze@usta.de \
--cc=joerg@britannica.bec.de \
--cc=tech@mdocml.bsd.lv \
--cc=wiz@NetBSD.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).