From: Pieter Wuille <pieter.wuille@gmail.com>
To: Gavin Andresen <gavinandresen@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] 0.8.0rc1 status
Date: Sat, 9 Feb 2013 07:10:34 +0100 [thread overview]
Message-ID: <CAPg+sBiGHnT1-W7m8RCt93-cZbpz0vxm+YQcnpFNXv7f-mrBXg@mail.gmail.com> (raw)
In-Reply-To: <CABsx9T1D08uOenXch7ZwrEaCeOdFCFOtzK8ochN8z3REGm0mLQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 257 bytes --]
On 9 Feb 2013 00:50, "Gavin Andresen" <gavinandresen@gmail.com> wrote:
> Then before final release (or rc2, if that is needed) pull #2286 and
> create and pull a patch to fix the windows non-determinism problem.
#2243 should fix that, I think.
--
Pieter
[-- Attachment #2: Type: text/html, Size: 395 bytes --]
next prev parent reply other threads:[~2013-02-09 6:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-08 23:49 [Bitcoin-development] 0.8.0rc1 status Gavin Andresen
2013-02-09 1:29 ` Luke-Jr
2013-02-09 4:11 ` grarpamp
2013-02-09 6:10 ` Pieter Wuille [this message]
2013-02-09 7:58 ` Robert Backhaus
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=CAPg+sBiGHnT1-W7m8RCt93-cZbpz0vxm+YQcnpFNXv7f-mrBXg@mail.gmail.com \
--to=pieter.wuille@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=gavinandresen@gmail.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