From: Kevin Carhart <firstname.lastname@example.org>
Subject: Re: [edbrowse-dev] spec > highspec
Date: Sun, 2 Jun 2019 21:25:38 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.email@example.com> (raw)
That makes sense, oh well. Onwards and upwards!
On Mon, 3 Jun 2019, Karl Dahlke wrote:
> I made the change, compiled, and got exactly the same result on the baseball site,
> and acid test 0 failed, which is sort of how I remembered it,
> and that's why I wrote it that way.
> Test 00 failed: expected 'pre-wrap' but got 'x-bogus' - found unexpected computed style
> Karl Dahlke
prev parent reply other threads:[~2019-06-03 4:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-03 2:03 Kevin Carhart
2019-06-03 4:10 ` Karl Dahlke
2019-06-03 4:25 ` Kevin Carhart [this message]
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).