From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] suggested additions
Date: Mon, 04 Sep 2017 11:06:47 -0400 [thread overview]
Message-ID: <20170804110647.eklhad@comcast.net> (raw)
In-Reply-To: <alpine.LRH.2.03.1709031908440.927@carhart.net>
Curious. Would the acid tests uncover these 7 things?
The jury is still out on whether we should follow the acid tests, or find&fix, or both.
Karl Dahlke
next prev parent reply other threads:[~2017-09-04 15:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-04 2:38 Kevin Carhart
2017-09-04 14:12 ` Karl Dahlke
2017-09-05 1:16 ` Kevin Carhart
2017-09-05 2:27 ` Karl Dahlke
2017-09-04 15:06 ` Karl Dahlke [this message]
2017-09-05 1:32 ` Kevin Carhart
2017-09-04 17:10 ` Karl Dahlke
2017-09-05 2:15 ` [Edbrowse-dev] contentWindow Kevin Carhart
[not found] ` <20170804223729.eklhad@comcast.net>
2017-09-05 2:58 ` Kevin Carhart
[not found] ` <20170804232757.eklhad@comcast.net>
2017-09-05 3:57 ` Kevin Carhart
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=20170804110647.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).