From: Chris Brannon <chris@the-brannons.com>
To: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] -Wall
Date: Tue, 25 Jul 2017 21:45:54 -0700 [thread overview]
Message-ID: <8760efdcvx.fsf@the-brannons.com> (raw)
In-Reply-To: <20170625230859.eklhad@comcast.net> (Karl Dahlke's message of "Tue, 25 Jul 2017 23:08:59 -0400")
Yes we should probably run with -Wall all the time.
Passing -O2 and -D_FORTIFY_SOURCE=2 in CFLAGS exposes more warnings.
Some of them should be taken very seriously.
-- Chris
next prev parent reply other threads:[~2017-07-26 4:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-26 3:08 Karl Dahlke
2017-07-26 4:45 ` Chris Brannon [this message]
2017-07-28 19:19 ` Adam Thompson
2017-07-27 18:21 ` Geoff McLane
2017-07-28 5:51 ` Karl Dahlke
2017-07-28 19:24 ` Geoff McLane
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=8760efdcvx.fsf@the-brannons.com \
--to=chris@the-brannons.com \
--cc=Edbrowse-dev@lists.the-brannons.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).