From: Matt Corallo <bitcoin-list@bluematt.me>
To: bitcoin-developmen@lists.sourceforge.net
Subject: [Bitcoin-development] 0.3.24 RC3 Build
Date: Wed, 06 Jul 2011 02:56:35 +0200 [thread overview]
Message-ID: <1309913732.29355.40.camel@Desktop666> (raw)
[-- Attachment #1: Type: text/plain, Size: 470 bytes --]
0.3.24 RC3 tar uploaded to http://dl.dropbox.com/u/29653426/Bitcoin%
200.3.24%20RC3.tar.bz2
I still disagree that 0.3.24 shouldn't handle incompatible wallets
cleanly, but I digress.
SHA1:
af85f46201bfffaf38fe4d64f3aa357ac03b51e1 Bitcoin 0.3.24 RC3.tar.bz2
Notes:
gitian-win32.yml is broken (my fault) just remove the lines
cp WSPiApi.h $HOME/build
#
and you should be on the same one as me.
Build gitian signed and email signed as always,
Matt
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
reply other threads:[~2011-07-06 0:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1309913732.29355.40.camel@Desktop666 \
--to=bitcoin-list@bluematt.me \
--cc=bitcoin-developmen@lists.sourceforge.net \
/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