From: Karl Dahlke <firstname.lastname@example.org>
Subject: [edbrowse-dev] v2-maintenance
Date: Tue, 10 Dec 2019 06:30:09 -0500 [thread overview]
Message-ID: <email@example.com> (raw)
As per https://www.digicatapult.org.uk/
Sami fixed the duktape bug that was revealed by this website.
The fix is in the v2-maintenance branch.
If you are following, he recommends this branch rather than master,
which is in a state of flux, but is probably ok for our purposes.
The fix is also in the master branch.
Or just stay with the duktape you have until 2.6 is released, or 3.0.
I am playing with v2-maintenance
reply other threads:[~2019-12-10 11:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).