public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: "Luke-Jr" <luke@dashjr.org>
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: Fri, 17 Jan 2014 21:31:15 +0000	[thread overview]
Message-ID: <201401172131.16598.luke@dashjr.org> (raw)
In-Reply-To: <CAJHLa0MVY6f02hK1CofM7bjLM=V1V0XKCWvHjBz=ozQdvA+xYA@mail.gmail.com>

On Friday, January 17, 2014 8:53:47 PM Jeff Garzik wrote:
> <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.

Heck, even I disagree with implementation details, but it's still better than 
nothing. We can always merge major reorganisations/reimplementations later 
when they're written: merging this one doesn't mean we're stuck with it 
forever...

Luke



  parent reply	other threads:[~2014-01-17 21:31 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 [this message]
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=201401172131.16598.luke@dashjr.org \
    --to=luke@dashjr.org \
    --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