From: Chris Brannon <chris@the-brannons.com>
To: Karl Dahlke <eklhad@comcast.net>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] 3.5.3
Date: Sat, 07 Feb 2015 08:34:05 -0800 [thread overview]
Message-ID: <87fvahr88y.fsf@mushroom.localdomain> (raw)
In-Reply-To: <20150106174819.eklhad@comcast.net> (Karl Dahlke's message of "Fri, 06 Feb 2015 17:48:19 -0500")
Karl Dahlke <eklhad@comcast.net> writes:
> When should we mark the next version?
I'd say let's do it soon. I've found a new bug with the html parser
though. It's segfaulting on some input, and I'm trying to track it
down. It's a regression, since 3.5.2 doesn't crash.
But maybe when we get that sorted out, 3.5.3 should be released.
-- Chris
next prev parent reply other threads:[~2015-02-07 16:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-06 22:48 Karl Dahlke
2015-02-07 16:24 ` Adam Thompson
2015-02-07 17:32 ` Chris Brannon
2015-02-07 16:34 ` Chris Brannon [this message]
2015-02-07 16:40 Karl Dahlke
2015-02-07 18:07 ` Adam Thompson
2015-02-09 14:07 Chris Brannon
2015-02-09 14:17 ` Adam Thompson
2015-02-09 14:26 Karl Dahlke
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=87fvahr88y.fsf@mushroom.localdomain \
--to=chris@the-brannons.com \
--cc=Edbrowse-dev@lists.the-brannons.com \
--cc=eklhad@comcast.net \
/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).