From: "Luke-Jr" <luke@dashjr•org>
To: Wladimir <laanwj@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Bitcoin Core 0.9rc1 release schedule
Date: Fri, 17 Jan 2014 18:41:36 +0000 [thread overview]
Message-ID: <201401171841.37790.luke@dashjr.org> (raw)
In-Reply-To: <CA+s+GJDeV9-djdEsA_stznNK9zzBA_0xQFV_m6tVygJicuLWuQ@mail.gmail.com>
On Friday, January 17, 2014 11:44:09 AM Wladimir wrote:
> On Thu, Jan 16, 2014 at 4:23 PM, Luke-Jr <luke@dashjr•org> wrote:
> > https://github.com/bitcoin/bitcoin/pulls/luke-jr
> >
> > These are pretty much all well-tested and stable for months now.
>
> #3242: Autoconf improvements needs rebase, and comment from jgarzik and me
> taken into account (about -enable-frontends=).
I'll try to get this done over the weekend.
> The others appear to be more controversial as they affect mining/consensus.
> I'd really like to see ACKs from more reviewers and testers there before
> merging.
Can you elaborate on this? I can see how Proposals might, if buggy, affect
consensus, but the rest shouldn't. I don't think there's anything
controversial in any of these (does someone disagree with CPFP?).
Luke
next prev parent reply other threads:[~2014-01-17 18:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-16 9:09 Wladimir
2014-01-16 10:41 ` Warren Togami Jr.
2014-01-16 15:23 ` Luke-Jr
2014-01-17 11:44 ` Wladimir
2014-01-17 18:41 ` Luke-Jr [this message]
2014-01-17 20:53 ` Jeff Garzik
2014-01-17 21:04 ` Mark Friedenbach
2014-01-18 11:34 ` Jouke Hofman
2014-01-17 21:31 ` Luke-Jr
2014-01-18 8:11 ` Odinn Cyberguerrilla
2014-01-18 11:05 ` Wladimir
2014-01-18 11:28 ` Odinn Cyberguerrilla
2014-01-18 17:38 ` Mark Friedenbach
2014-01-19 2:53 ` Jeff Garzik
2014-01-19 10:24 ` Wladimir
2014-01-23 11:10 ` Wladimir
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=201401171841.37790.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=laanwj@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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