public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Tom Zander <tomz@freedommail.ch>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Barry Silbert segwit agreement
Date: Sat, 27 May 2017 00:12:49 +0200	[thread overview]
Message-ID: <16817995.6UCILLkEDc@strawberry> (raw)
In-Reply-To: <CADvTj4o2pFXZFHALfP-dJ10+AQxfFLVuohcpBn-tupf+CHRBYA@mail.gmail.com>

On Friday, 26 May 2017 23:30:37 CEST James Hilliard via bitcoin-dev wrote:
> It would not be feasible to schedule any HF until one can be
> completely sure BIP141 is active

why?

> Since it is likely a HF will take months of development and testing I
> see this or something similar as the fastest safe path forward

This should not be an issue, it started 2 years ago. Its tested.
-- 
Tom Zander
Blog: https://zander.github.io
Vlog: https://vimeo.com/channels/tomscryptochannel


  reply	other threads:[~2017-05-26 22:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-26 17:47 [bitcoin-dev] Barry Silbert segwit agreement Jacob Eliosoff
2017-05-26 18:48 ` Tom Zander
2017-05-26 20:02 ` Matt Corallo
2017-05-26 20:10   ` Jacob Eliosoff
2017-05-26 21:30     ` James Hilliard
2017-05-26 22:12       ` Tom Zander [this message]
     [not found]         ` <CADvTj4qdr2yGYFEWA7oVmL-KkrchYb5aQBRY9w0OK4ZVopSTSA@mail.gmail.com>
2017-05-28 20:51           ` Tom Zander
2017-05-28 23:28             ` James Hilliard
2017-05-26 22:44       ` Matt Corallo
  -- strict thread matches above, loose matches on Subject: below --
2017-05-22 12:29 Daniele Pinna
2017-05-22  6:12 shaolinfry
2017-05-22  6:27 ` Peter Todd
2017-05-22  9:23 ` Hampus Sjöberg

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=16817995.6UCILLkEDc@strawberry \
    --to=tomz@freedommail.ch \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    /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