From: Chris Brannon <chris@the-brannons.com>
To: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] Issues reported by Clang static analyzer
Date: Tue, 05 Aug 2014 04:28:54 -0700 [thread overview]
Message-ID: <87tx5rkweh.fsf@mushroom.PK5001Z> (raw)
In-Reply-To: <20140705071103.eklhad@comcast.net> (Karl Dahlke's message of "Tue, 05 Aug 2014 07:11:03 -0400")
Karl Dahlke <eklhad@comcast.net> writes:
> I think it was fine the way it was, really,
> would only cause trouble on a situation that I know can never occur,
Yes, I'm all for fixing these, even when we can prove that they're
spurious. I'm happy to work on more of them.
Oh, and Paul asked which method was best for sending contributions to
edbrowse. Patches to the list are the best, so that either Karl, Adam,
or myself can review them.
Thanks,
-- Chris
next prev parent reply other threads:[~2014-08-05 11:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-05 11:11 Karl Dahlke
2014-08-05 11:28 ` Chris Brannon [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-07-31 7: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=87tx5rkweh.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).