source@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: schwarze@mandoc.bsd.lv
To: source@mandoc.bsd.lv
Subject: mandoc: NULL requires <stddef.h>
Date: Tue, 14 Aug 2018 21:49:21 -0500 (EST)	[thread overview]
Message-ID: <c89effea4d5d2e50@fantadrom.bsd.lv> (raw)

Log Message:
-----------
NULL requires <stddef.h>

Modified Files:
--------------
    mandoc:
        test-stringlist.c

Revision Data
-------------
Index: test-stringlist.c
===================================================================
RCS file: /home/cvs/mandoc/mandoc/test-stringlist.c,v
retrieving revision 1.2
retrieving revision 1.3
diff -Ltest-stringlist.c -Ltest-stringlist.c -u -p -r1.2 -r1.3
--- test-stringlist.c
+++ test-stringlist.c
@@ -15,6 +15,7 @@
  * OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
  */
 
+#include <stddef.h>
 #include <stringlist.h>
 
 int
--
 To unsubscribe send an email to source+unsubscribe@mandoc.bsd.lv

                 reply	other threads:[~2018-08-15  2:49 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=c89effea4d5d2e50@fantadrom.bsd.lv \
    --to=schwarze@mandoc.bsd.lv \
    --cc=source@mandoc.bsd.lv \
    /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).