From: Wladimir <laanwj@gmail.com>
To: Jeff Garzik <jgarzik@bitpay.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Bitcoin Core 0.9rc1 release schedule
Date: Sun, 19 Jan 2014 11:24:08 +0100 [thread overview]
Message-ID: <CA+s+GJDFq0P+cgAVL9N1ADT7PFB4eMSPnoSR05wPOB5KRL-C+g@mail.gmail.com> (raw)
In-Reply-To: <CAJHLa0PAG=2+GOiLWYgWH81q+eAQ4w3LdDDemQ9J0K0AddUw_w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 630 bytes --]
On Sun, Jan 19, 2014 at 3:53 AM, Jeff Garzik <jgarzik@bitpay.com> wrote:
> 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.
>
The only thing controversial are the code changes themselves, not the
feature.
Consensus running through the comments in the pull is that it needs
(auto)tests.
Are you going to do this Luke? Or is anyone else working on this?
Wladimir
[-- Attachment #2: Type: text/html, Size: 1304 bytes --]
next prev parent reply other threads:[~2014-01-19 10:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-16 9:09 [Bitcoin-development] Bitcoin Core 0.9rc1 release schedule 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
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 [this message]
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=CA+s+GJDFq0P+cgAVL9N1ADT7PFB4eMSPnoSR05wPOB5KRL-C+g@mail.gmail.com \
--to=laanwj@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=jgarzik@bitpay.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