public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Peter Todd <pete@petertodd•org>
To: Pieter Wuille <pieter.wuille@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Bitcoin core 0.11 planning
Date: Tue, 28 Apr 2015 09:42:38 -0400	[thread overview]
Message-ID: <20150428134238.GA11026@muck> (raw)
In-Reply-To: <CAPg+sBjc4iguJ8KCnUf9LrLbPkWEMc5fvr7XZsA48XQKaecN5g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 601 bytes --]

On Tue, Apr 28, 2015 at 04:01:00AM -0700, Pieter Wuille wrote:
> As softforks almost certainly require backports to older releases and other
> software anyway, I don't think they should necessarily be bound to Bitcoin
> Core major releases. If they don't require large code changes, we can
> easily do them in minor releases too.

The code changes for absolute CLTV are quite small, and easily ported to
any Bitcoin Core version.

What's the oldest version you think we need backports for?

-- 
'peter'[:-1]@petertodd.org
00000000000000000e7980aab9c096c46e7f34c43a661c5cb2ea71525ebb8af7

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 650 bytes --]

  reply	other threads:[~2015-04-28 13:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-28  7:44 Wladimir J. van der Laan
2015-04-28 10:49 ` Peter Todd
2015-04-28 11:01   ` Pieter Wuille
2015-04-28 13:42     ` Peter Todd [this message]
     [not found]     ` <CA+s+GJBeZkWSKn4igC1ksynoQLfUpUtHBesq9MPi6yRqZZr4Gw@mail.gmail.com>
2015-05-11 14:49       ` [Bitcoin-development] Fwd: " Wladimir
2015-05-11 15:00 ` [Bitcoin-development] " 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=20150428134238.GA11026@muck \
    --to=pete@petertodd$(echo .)org \
    --cc=bitcoin-development@lists$(echo .)sourceforge.net \
    --cc=pieter.wuille@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