From: Kevin Carhart <kevin@carhart.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [edbrowse-dev] interdirectory moves, and indent
Date: Sat, 18 Jul 2020 22:06:31 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.21.2007182153550.1637@phoenix> (raw)
> Probably none of you fiddle with edbrowse code any more,
> but if any of you do, this is a heads up.
I actually have been trying to get nasa.gov back recently. It might have
something to do with nonprinting characters that occur in strings
in vendor.js. I think vendor.js may have been changed since the times
when we got nasa.gov working.
next reply other threads:[~2020-07-19 5:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-19 5:06 Kevin Carhart [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-07-14 16:49 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=alpine.DEB.2.21.2007182153550.1637@phoenix \
--to=kevin@carhart.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).