public inbox for edbrowse-dev@edbrowse.org
 help / color / mirror / Atom feed
From: Chris Brannon <chris@the-brannons.com>
To: Karl Dahlke <eklhad@comcast.net>,  edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] 3.6.0?
Date: Wed, 02 Dec 2015 18:42:49 -0800	[thread overview]
Message-ID: <87k2owqml2.fsf@mushroom.localdomain> (raw)
In-Reply-To: <alpine.LRH.2.03.1512021758570.24417@carhart.net> (Kevin Carhart's message of "Wed, 2 Dec 2015 17:59:24 -0800 (PST)")

Kevin Carhart <kevin@carhart.net> writes:

> Coming soon.  Coming this evening.

It's all good, I don't think anyone's in a hurry, and this sounds like
some awesome work!

-- Chris

  reply	other threads:[~ UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Chris Brannon
 ` Karl Dahlke
   ` Kevin Carhart
     ` Chris Brannon [this message]
       ` Kevin Carhart
         ` Karl Dahlke
           ` Kevin Carhart
             ` Karl Dahlke
               ` [Edbrowse-dev] jquery v2 and an interesting seg fault Kevin Carhart
                 ` Karl Dahlke
                   ` Kevin Carhart
                     ` [Edbrowse-dev] javascript() in timer side effects Kevin Carhart
                       ` Karl Dahlke
                         ` Kevin Carhart
                           ` Karl Dahlke
                             ` Kevin Carhart
                               ` Adam Thompson

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=87k2owqml2.fsf@mushroom.localdomain \
    --to=chris@the-brannons.com \
    --cc=edbrowse-dev@lists.the-brannons.com \
    --cc=eklhad@comcast.net \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).