From: Karl Dahlke <eklhad@comcast.net>
To: edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] duktape version requirements
Date: Thu, 11 Jan 2018 06:57:48 -0500 [thread overview]
Message-ID: <20180011065748.eklhad@comcast.net> (raw)
In-Reply-To: <alpine.DEB.2.21.1801110647460.22495@debian.pulsar.com>
[-- Attachment #1: Type: text/plain, Size: 372 bytes --]
I'm on 2.2.0-46, but your versions will likely work.
A couple of bugs found and fixed since then, but the API holds steady.
If we can't track down our problems, just aren't making any headway, you can build and use the latest duktape as per the instructions in README.
I doubt that's the source of your amazon problems though, but who can say for sure.
Karl Dahlke
prev parent reply other threads:[~2018-01-11 11:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-11 11:51 Chuck Hallenbeck
2018-01-11 11:57 ` Karl Dahlke [this message]
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=20180011065748.eklhad@comcast.net \
--to=eklhad@comcast.net \
--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).