From: Chris Brannon <chris@the-brannons.com>
To: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] master
Date: Tue, 28 Jan 2014 08:41:18 -0800 [thread overview]
Message-ID: <87lhy0m53l.fsf@mushroom.PK5001Z> (raw)
In-Reply-To: <20140028062012.eklhad@comcast.net> (Karl Dahlke's message of "Tue, 28 Jan 2014 06:20:12 -0500")
> if Adam then had permission to push into masster, as I do,
I have no problem with that. He has more than proven his capability to
me. I would also like to see these changes merged into master, so more
people can test and help us find problems.
Adam, you can now push to the main repository.
Please merge whenever you're ready.
> A piece of my brain thinks there should be some backward compatibility,
> like a flag to makefile to build the old way against 185,
Well, it would require a lot of backward-compatibility code. Let's not
go there.
> the only thing we really have to stop nad pause and well test is the threshold
> of version 3.4.11.
Right. In fact, I'd be inclined to bump the minor number: 3.5.0 instead
of 3.4.11. But we aren't ready for that yet.
-- Chris
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
Karl Dahlke
` Chris Brannon [this message]
` Adam Thompson
` Adam Thompson
` Chris Brannon
` Cleverson Casarin Uliana
` Adam Thompson
Karl Dahlke
` Adam Thompson
Karl Dahlke
` Chris Brannon
` 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=87lhy0m53l.fsf@mushroom.PK5001Z \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).