From: Rusty Russell <rusty@rustcorp.com.au>
To: Matt Corallo <lf-lists@mattcorallo.com>,
Gregory Maxwell <greg@xiph.org>,
Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP149 timeout-- why so far in the future?
Date: Sat, 27 May 2017 10:49:33 +0930 [thread overview]
Message-ID: <87inkn14gq.fsf@rustcorp.com.au> (raw)
In-Reply-To: <63d03825-da9b-328d-56b8-0d062f3e0c62@mattcorallo.com>
Matt Corallo <lf-lists@mattcorallo.com> writes:
> A more important consideration than segwit's timeout is when code can be
> released, which will no doubt be several months after SegWit's current
> timeout.
I was assuming it would be included in the next point release.
Cheers,
Rusty.
next prev parent reply other threads:[~2017-05-27 10:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-23 17:50 [bitcoin-dev] BIP149 timeout-- why so far in the future? Gregory Maxwell
2017-05-24 4:26 ` Rusty Russell
2017-05-26 20:04 ` Matt Corallo
2017-05-27 1:19 ` Rusty Russell [this message]
2017-06-11 5:48 ` Ryan Grant
2017-06-11 13:17 ` Jorge Timón
2017-05-26 7:28 ` shaolinfry
2017-06-11 13:44 Martijn Meijering
2017-06-11 14:29 ` Jorge Timón
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=87inkn14gq.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=greg@xiph.org \
--cc=lf-lists@mattcorallo.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