From: Matt Corallo <bitcoin-list@bluematt•me>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] 0.4 Release Candidate 2
Date: Fri, 09 Sep 2011 19:49:17 -0400 [thread overview]
Message-ID: <1315612157.3544.2.camel@BMThinkPad.lan.bluematt.me> (raw)
In-Reply-To: <CABsx9T2Y3CmBr=twHvFOEoQCVcSySZ+JyEQXcOseRKxJi3KoLw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 989 bytes --]
On Fri, 2011-09-09 at 10:02 -0400, Gavin Andresen wrote:
> I just tagged the git tree: v0.4.00rc2
>
> Fixes from release candidate 1:
>
> + Optimize database writes for transactions with lots of inputs
> + Fix a deadlock that could occur when adding addresses from 'addr'
> messages and irc
> + Fix a potential problem with duplicate, un-spendable coinbase
> transactions if you were generating bitcoins, with a locked wallet,
> and ran out of keypool keys.
>
>
I'm too lazy to make nice tars so here is the raw gitian output (I plan
on working out gitian-downloader stuff sometime in the next couple
days).
Also, setup exe still not deterministic so theres that...
Anyway:
http://dl.dropbox.com/u/29653426/bitcoin-ubuntu-v0.4.00rc2.zip
http://dl.dropbox.com/u/29653426/bitcoin-win32-v0.4.00rc2.zip
SHA1s:
fd886d79bf48ba0d90f2f99fdd19d96946662bf5 bitcoin-ubuntu-v0.4.00rc2.zip
703712859ecdce423020116ebf65d087b179997d bitcoin-win32-v0.4.00rc2.zip
Matt
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2011-09-09 23:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-09 14:02 Gavin Andresen
2011-09-09 23:49 ` Matt Corallo [this message]
2011-09-10 5:18 ` Jeff Garzik
2011-09-16 16:38 ` Jeff Garzik
2011-09-22 7:46 ` Martinx - ジェームズ
2011-09-22 22:25 ` John Smith
2011-09-22 22:55 ` Martinx - ジェームズ
2011-09-23 1:20 ` Martinx - ジェームズ
2011-09-23 2:05 ` Martinx - ジェームズ
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=1315612157.3544.2.camel@BMThinkPad.lan.bluematt.me \
--to=bitcoin-list@bluematt$(echo .)me \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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