From: Chris Brannon <chris@the-brannons.com>
To: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] ifndef CURLE_PEER_FAILED_VERIFICATION
Date: Wed, 06 Aug 2014 10:19:24 -0700 [thread overview]
Message-ID: <87ha1plen7.fsf@mushroom.PK5001Z> (raw)
In-Reply-To: <20140706101426.eklhad@comcast.net> (Karl Dahlke's message of "Wed, 06 Aug 2014 10:14:26 -0400")
Karl Dahlke <eklhad@comcast.net> writes:
> Chris I think you put those in, what do you think?
I honestly don't remember doing that, but I probably did, way back in
2008. If there was a good reason for doing it back then, it's no longer
valid, so let's remove them.
On another note, I have a patch that eliminates a third of those clang
warnings, just by using some source annotations. A bunch of warnings
are spurious, because clang has no way of proving that some functions
(showErrorAbort, i_printfExit) will never return. Source annotations
help here. I'm looking at the rest as well, and I'll make up a set of
several patches.
-- Chris
next prev parent reply other threads:[~2014-08-06 17:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-06 14:14 Karl Dahlke
2014-08-06 17:19 ` Chris Brannon [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-08-06 18:39 Karl Dahlke
2014-08-06 13:54 Paul Onyschuk
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=87ha1plen7.fsf@mushroom.PK5001Z \
--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).