From: Wladimir <laanwj@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: [Bitcoin-development] 0.9.0rc3 tagged
Date: Thu, 13 Mar 2014 12:11:52 +0100 [thread overview]
Message-ID: <CA+s+GJBVsnjQhip8k=r-HYj6T6S4A3ov04LFwMHKMGWwMyO5jQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 368 bytes --]
Haven't seen any message about this on the mailing list yet, so FYI:
0.9.0rc3 has been tagged.
The significant change compared to rc2 is that the mining code fee policy
now matches relay fee policy.
Also a rare crash in the wallet code was fixed.
There are some further small build system, documentation and GUI changes.
Please start your gitian builds.
Wladimir
[-- Attachment #2: Type: text/html, Size: 550 bytes --]
next reply other threads:[~2014-03-13 11:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-13 11:11 Wladimir [this message]
2014-03-13 12:25 ` [Bitcoin-development] 0.9.0rc3 tagged Gavin Andresen
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='CA+s+GJBVsnjQhip8k=r-HYj6T6S4A3ov04LFwMHKMGWwMyO5jQ@mail.gmail.com' \
--to=laanwj@gmail.com \
--cc=bitcoin-development@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