discuss@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Stephen Gregoratto <dev@sgregoratto.me>
To: discuss@mandoc.bsd.lv
Cc: christos@netbsd.org
Subject: Re: man_validate.c compile errors on Linux gcc/clang
Date: Thu, 14 Mar 2019 12:11:29 +1100	[thread overview]
Message-ID: <20190314011129.kgfy6lprybkzz4os@BlackBox> (raw)
In-Reply-To: <20190313183814.GC46802@athene.usta.de>

On 2019-03-13 19:38, Ingo Schwarze wrote:
> Thank you for reporting this issue.
> I (hopefully) fixed it with the commit below.
> Can you confirm that the fix works?
Yes, it does. Thanks for your help Ingo. I've actually found another 
(small) error with gcc on SunOS 5.10, but I'll put that under a new 
topic.
-- 
Stephen Gregoratto
PGP: 3FC6 3D0E 2801 C348 1C44 2D34 A80C 0F8E 8BAB EC8B
--
 To unsubscribe send an email to discuss+unsubscribe@mandoc.bsd.lv

  reply	other threads:[~2019-03-14  1:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-13  1:32 Stephen Gregoratto
2019-03-13 18:38 ` Ingo Schwarze
2019-03-14  1:11   ` Stephen Gregoratto [this message]
2019-03-14  1:30     ` Stephen Gregoratto
2019-03-14 11:45     ` 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=20190314011129.kgfy6lprybkzz4os@BlackBox \
    --to=dev@sgregoratto.me \
    --cc=christos@netbsd.org \
    --cc=discuss@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).