1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <jgarzik@bitpay.com>) id 1W4GQM-0006xr-L0
for bitcoin-development@lists.sourceforge.net;
Fri, 17 Jan 2014 20:53:54 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of bitpay.com
designates 209.85.212.180 as permitted sender)
client-ip=209.85.212.180; envelope-from=jgarzik@bitpay.com;
helo=mail-wi0-f180.google.com;
Received: from mail-wi0-f180.google.com ([209.85.212.180])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1W4GQL-0000r6-Pa
for bitcoin-development@lists.sourceforge.net;
Fri, 17 Jan 2014 20:53:54 +0000
Received: by mail-wi0-f180.google.com with SMTP id d13so1235015wiw.7
for <bitcoin-development@lists.sourceforge.net>;
Fri, 17 Jan 2014 12:53:47 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:in-reply-to:references:date
:message-id:subject:from:to:cc:content-type;
bh=8pcrUwpmVhjVsFJI/d2k7cU4fUQkHoehLzuuOnZZXe4=;
b=OnMnHKp8v/meCWrSY1b4OFWk+flT3LH9mlfsGHlPrW6q8xJ0BkMrhq1l4MtMucM8V5
/wU/7pfMueG3IIqu6mkKLmglepo/8AsbSuFJ2sm7DjrcE1WZwSR4kkVwzNLq3XFselFW
AWIr26g1zTCgdXUcm3DSmX3N3d004xMVpz2QY6y0PmtP8HvF7WLnahNXqvrW/pxYs4Wt
LTKSN5aske6R/L0Tc62LaargHLWxYMJSKxkeNoJhq2oob28ZA60n8znm0zPxA4g8vtWO
1jt8Hrc4Sj71xm1R7eQwY3Q5FK31PpV2k3b/48peWhkCjVp6ny8Uuz4mrdb/g1BY15Yw
sbGg==
X-Gm-Message-State: ALoCoQm1Br18JTQ2h01QP4oXkz9Nz6BCVroBv5p9htKEY4qeK6S4OIRfDyl1QNM+yLOu9/38SDxu
MIME-Version: 1.0
X-Received: by 10.195.13.130 with SMTP id ey2mr3903076wjd.7.1389992027507;
Fri, 17 Jan 2014 12:53:47 -0800 (PST)
Received: by 10.194.2.164 with HTTP; Fri, 17 Jan 2014 12:53:47 -0800 (PST)
In-Reply-To: <201401171841.37790.luke@dashjr.org>
References: <CA+s+GJBo7iUEJTfJw2e6qcDmdHNGdDN442Svs5ikVyUL1Jm0Wg@mail.gmail.com>
<201401161523.38623.luke@dashjr.org>
<CA+s+GJDeV9-djdEsA_stznNK9zzBA_0xQFV_m6tVygJicuLWuQ@mail.gmail.com>
<201401171841.37790.luke@dashjr.org>
Date: Fri, 17 Jan 2014 15:53:47 -0500
Message-ID: <CAJHLa0MVY6f02hK1CofM7bjLM=V1V0XKCWvHjBz=ozQdvA+xYA@mail.gmail.com>
From: Jeff Garzik <jgarzik@bitpay.com>
To: Luke-Jr <luke@dashjr.org>
Content-Type: text/plain; charset=ISO-8859-1
X-Spam-Score: -1.6 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
-0.0 SPF_PASS SPF: sender matches SPF record
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1W4GQL-0000r6-Pa
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Bitcoin Core 0.9rc1 release schedule
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Fri, 17 Jan 2014 20:53:54 -0000
<vendor hat: on> BitPay sure would like to see CPFP in upstream.
I think the main hurdle to merging was that various people disagreed
on various edge case handling and implementation details, but no
fundamental objections.
On Fri, Jan 17, 2014 at 1:41 PM, Luke-Jr <luke@dashjr.org> wrote:
> 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
>
> ------------------------------------------------------------------------------
> CenturyLink Cloud: The Leader in Enterprise Cloud Services.
> Learn Why More Businesses Are Choosing CenturyLink Cloud For
> Critical Workloads, Development Environments & Everything In Between.
> Get a Quote or Start a Free Trial Today.
> http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
--
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc. https://bitpay.com/
|
