From: Kevin Carhart <kevin@carhart.net>
To: edbrowse-dev@lists.the-brannons.com
Subject: [edbrowse-dev] happy new year
Date: Mon, 31 Dec 2018 00:32:45 -0800 (PST) [thread overview]
Message-ID: <alpine.LRH.2.03.1812310030020.9774@carhart.net> (raw)
Hope everyone is doing all right. I was thinking about this list as a
social scene and source of very challenging problems with some successful
pragmatic outcomes for the browser users, as well as a lot that is over
our heads and I would like to address but can't wrap my brain around it.
I'm thankful for edbrowse and edbrowse-dev too.
Best wishes to the list subscribers who I've had the pleasure to
talk to either frequently or once in a while. I hope you have good
health, happiness and that 2019 is a good year for you.
Kevin
next reply other threads:[~2018-12-31 8:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-31 8:32 Kevin Carhart [this message]
2018-12-31 10:57 ` Chuck Hallenbeck
2018-12-31 12:21 ` 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.LRH.2.03.1812310030020.9774@carhart.net \
--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).