diff options
author | Mike Hearn <mike@plan99.net> | 2012-12-24 17:21:26 +0100 |
---|---|---|
committer | bitcoindev <bitcoindev@gnusha.org> | 2012-12-24 16:21:32 +0000 |
commit | 3aa9a0a90521baa4d7e2d504ad5226f9fb1c0b73 (patch) | |
tree | ecaa94995fe7458d8ae0b278250f5b65c524fb07 | |
parent | 0efa7aad548118ccad6d2abff14ac2f406d22bcd (diff) | |
download | pi-bitcoindev-3aa9a0a90521baa4d7e2d504ad5226f9fb1c0b73.tar.gz pi-bitcoindev-3aa9a0a90521baa4d7e2d504ad5226f9fb1c0b73.zip |
Re: [Bitcoin-development] Testnet3 difficulty transition problem?
-rw-r--r-- | c8/9bbf824b721fca8881bfb7aa4b12e9d9b6f742 | 63 |
1 files changed, 63 insertions, 0 deletions
diff --git a/c8/9bbf824b721fca8881bfb7aa4b12e9d9b6f742 b/c8/9bbf824b721fca8881bfb7aa4b12e9d9b6f742 new file mode 100644 index 000000000..71d396ba9 --- /dev/null +++ b/c8/9bbf824b721fca8881bfb7aa4b12e9d9b6f742 @@ -0,0 +1,63 @@ +Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] + helo=mx.sourceforge.net) + by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) + (envelope-from <mh.in.england@gmail.com>) id 1TnAmS-0000nV-Iz + for bitcoin-development@lists.sourceforge.net; + Mon, 24 Dec 2012 16:21:32 +0000 +Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com + designates 209.85.219.44 as permitted sender) + client-ip=209.85.219.44; envelope-from=mh.in.england@gmail.com; + helo=mail-oa0-f44.google.com; +Received: from mail-oa0-f44.google.com ([209.85.219.44]) + by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) + (Exim 4.76) id 1TnAmR-00057u-PZ + for bitcoin-development@lists.sourceforge.net; + Mon, 24 Dec 2012 16:21:32 +0000 +Received: by mail-oa0-f44.google.com with SMTP id n5so6956225oag.31 + for <bitcoin-development@lists.sourceforge.net>; + Mon, 24 Dec 2012 08:21:26 -0800 (PST) +MIME-Version: 1.0 +Received: by 10.60.30.42 with SMTP id p10mr6235209oeh.59.1356366086499; Mon, + 24 Dec 2012 08:21:26 -0800 (PST) +Sender: mh.in.england@gmail.com +Received: by 10.76.128.139 with HTTP; Mon, 24 Dec 2012 08:21:26 -0800 (PST) +In-Reply-To: <CAAS2fgTM6n17x+3Oen78LHeAVuyOaXLCy285NKqqCLN74VB_=Q@mail.gmail.com> +References: <kb4upt$9vo$1@ger.gmane.org> + <CAAS2fgQKidxKmJ47oDi80YZrTW_MrVYf_u_tcZtO+xv2o+8S+w@mail.gmail.com> + <CAAS2fgTM6n17x+3Oen78LHeAVuyOaXLCy285NKqqCLN74VB_=Q@mail.gmail.com> +Date: Mon, 24 Dec 2012 17:21:26 +0100 +X-Google-Sender-Auth: ZSLpumwzUq0Rb6aYCT1wcy3qIig +Message-ID: <CANEZrP2-5ktJM2m5pnf5cxTTbpFgTnhnrbh5uHo0JtbJqkDXrw@mail.gmail.com> +From: Mike Hearn <mike@plan99.net> +To: Gregory Maxwell <gmaxwell@gmail.com> +Content-Type: text/plain; charset=UTF-8 +X-Spam-Score: -1.5 (-) +X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. + See http://spamassassin.org/tag/ for more details. + -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for + sender-domain + 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider + (mh.in.england[at]gmail.com) + -0.0 SPF_PASS SPF: sender matches SPF record + 0.1 DKIM_SIGNED Message has a DKIM or DK signature, + not necessarily valid + -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature +X-Headers-End: 1TnAmR-00057u-PZ +Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net> +Subject: Re: [Bitcoin-development] Testnet3 difficulty transition problem? +X-BeenThere: bitcoin-development@lists.sourceforge.net +X-Mailman-Version: 2.1.9 +Precedence: list +List-Id: <bitcoin-development.lists.sourceforge.net> +List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, + <mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe> +List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development> +List-Post: <mailto:bitcoin-development@lists.sourceforge.net> +List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help> +List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, + <mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe> +X-List-Received-Date: Mon, 24 Dec 2012 16:21:32 -0000 + +I pushed a fix for this. + + |