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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <jgarzik@bitpay.com>) id 1W4iVh-00025B-59
for bitcoin-development@lists.sourceforge.net;
Sun, 19 Jan 2014 02:53:17 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of bitpay.com
designates 209.85.212.170 as permitted sender)
client-ip=209.85.212.170; envelope-from=jgarzik@bitpay.com;
helo=mail-wi0-f170.google.com;
Received: from mail-wi0-f170.google.com ([209.85.212.170])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1W4iVf-0008GM-Vf
for bitcoin-development@lists.sourceforge.net;
Sun, 19 Jan 2014 02:53:17 +0000
Received: by mail-wi0-f170.google.com with SMTP id ex4so3354216wid.3
for <bitcoin-development@lists.sourceforge.net>;
Sat, 18 Jan 2014 18:53:09 -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=jAsw9tN61RE43chwbxEk13aKSmd5rWb1fVn4G1Zyn9Y=;
b=aWCu9fxndi5KrAkS6dHaQLyFgEW7ieEu81Gh6dX9XXx30OdfffzVZx81Bik9vsoTZI
Ox6wZmjtECouInG8k4+CcVOmmGRD5R74OPQtxr6Y5Wth71UHNCf5N584rlFXH9XO72Wb
QTEAO8JjqQ8otha9iCXTcy7V4dxo1GjILdumjShAzOcyKpTldJqE2gd8dZJpq/ocR2K/
4LlSWgV36iRUDzbRPaCoKk+r8STpDIvtnJJCIjWnFm95s9dC0ELAZSQeY/8PwtsGJM28
1EZZoaTlKB35Q4U571Pxj9JWF+Y3pSd1v7ux/xEH6GAWdFgGY2GxFQYagQPr/Af0odLP
RiIA==
X-Gm-Message-State: ALoCoQnIPy6tKXeHIHvcZpl2Im6etCUiWz813JFXncMBYAlWGHXhvCdZhLw/U8NuZk8pjF6Ct069
MIME-Version: 1.0
X-Received: by 10.180.182.226 with SMTP id eh2mr4421731wic.36.1390099989738;
Sat, 18 Jan 2014 18:53:09 -0800 (PST)
Received: by 10.194.2.164 with HTTP; Sat, 18 Jan 2014 18:53:09 -0800 (PST)
In-Reply-To: <52DABC0D.8060900@monetize.io>
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>
<CAJHLa0MVY6f02hK1CofM7bjLM=V1V0XKCWvHjBz=ozQdvA+xYA@mail.gmail.com>
<61c05e986b4d1010d0cf76868db7d2af.squirrel@fruiteater.riseup.net>
<CA+s+GJCwB3Jj7z32_5NCHgf7utyx0nm-fXiSW+79w8u4mi7W5g@mail.gmail.com>
<52DABC0D.8060900@monetize.io>
Date: Sat, 18 Jan 2014 21:53:09 -0500
Message-ID: <CAJHLa0PAG=2+GOiLWYgWH81q+eAQ4w3LdDDemQ9J0K0AddUw_w@mail.gmail.com>
From: Jeff Garzik <jgarzik@bitpay.com>
To: Mark Friedenbach <mark@monetize.io>
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: 1W4iVf-0008GM-Vf
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: Sun, 19 Jan 2014 02:53:17 -0000
There's a reason why luke-jr's pull request for CPfP remains open.
There is general agreement that it appears to be useful. CPfP works
to close the mismatch between how bitcoin transaction fees are
attached by the sender, versus modern economic situations where the
receiver is willing to pay a fee.
On Sat, Jan 18, 2014 at 12:38 PM, Mark Friedenbach <mark@monetize.io> wrote:
> On 01/18/2014 03:05 AM, Wladimir wrote:
>> On Sat, Jan 18, 2014 at 9:11 AM, Odinn Cyberguerrilla
>>
>> <ABISprotocol hat: on>
>>
>> regarding:
>> stuff not getting into blockchain in a day's time,
>> microdonations not facilitated as much as they could be,
>>
>> Please point to your pull requests improving these issues.
>>
>> If your organization didn't contribute anything to further these issues
>> then there can't be much surprise that they didn't make it in, either.
>
> https://github.com/bitcoin/bitcoin/pull/1647
>
> ------------------------------------------------------------------------------
> 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/
|
