From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] Named Pipes
Date: Sat, 09 Jan 2016 11:36:12 -0500 [thread overview]
Message-ID: <20160009113612.eklhad@comcast.net> (raw)
In-Reply-To: <20160109142626.GA6360@122oven.adamthompson.me.uk>
> I'm wondering if we should start work on 3.7 at this point,
Well I'll let you and Chris manage version numbers,
I don't have strong feelings about that.
Karl Dahlke
next prev parent reply other threads:[~2016-01-09 16:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160008145150.eklhad@comcast.net>
[not found] ` <20160109082016.GA2925@122oven.adamthompson.me.uk>
2016-01-09 13:12 ` Karl Dahlke
2016-01-09 14:26 ` Adam Thompson
2016-01-09 16:36 ` Karl Dahlke [this message]
2016-01-17 7:34 ` Chris Brannon
2016-01-17 10:16 ` 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=20160009113612.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).