From: Chris Brannon <chris@the-brannons.com>
To: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] Named Pipes
Date: Sat, 16 Jan 2016 23:34:37 -0800 [thread overview]
Message-ID: <87pox04q2a.fsf@mushroom.localdomain> (raw)
In-Reply-To: <20160109142626.GA6360@122oven.adamthompson.me.uk> (Adam Thompson's message of "Sat, 9 Jan 2016 14:26:26 +0000")
Adam Thompson <arthompson1990@gmail.com> writes:
> I'm wondering if we should start work on 3.7 at this point,
> hold off the release to get the major changes in.
> This is going to be a big change and I'm not sure I want to have minor releases
> differ quite so much when it comes to IPC.
Really it shouldn't be a user-visible change. It shouldn't break your
build, and it shouldn't break backward compatibility. So I'd say stick
with putting it in a minor version number. Remember how big 3.6.0 was?
But let's get past named pipes and IPC. Once we have them in, working,
and well-tested, we can decide which version we want to put out next, or
whether we want to keep going and try to add more features.
We're good to go for a 3.6.1 though, I believe.
Just give the word.
-- Chris
next prev parent reply other threads:[~2016-01-17 7:33 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
2016-01-17 7:34 ` Chris Brannon [this message]
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=87pox04q2a.fsf@mushroom.localdomain \
--to=chris@the-brannons.com \
--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).