blob: 18ed20331fba36c2f20ea40a1eb8d3f684a94f19 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <laanwj@gmail.com>) id 1YJLcj-00042x-Jo
for bitcoin-development@lists.sourceforge.net;
Thu, 05 Feb 2015 12:33:33 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.223.181 as permitted sender)
client-ip=209.85.223.181; envelope-from=laanwj@gmail.com;
helo=mail-ie0-f181.google.com;
Received: from mail-ie0-f181.google.com ([209.85.223.181])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1YJLci-0004pq-P6
for bitcoin-development@lists.sourceforge.net;
Thu, 05 Feb 2015 12:33:33 +0000
Received: by mail-ie0-f181.google.com with SMTP id rd18so9621301iec.12
for <bitcoin-development@lists.sourceforge.net>;
Thu, 05 Feb 2015 04:33:27 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.43.126.67 with SMTP id gv3mr7040019icc.31.1423139607514;
Thu, 05 Feb 2015 04:33:27 -0800 (PST)
Received: by 10.64.147.196 with HTTP; Thu, 5 Feb 2015 04:33:27 -0800 (PST)
Date: Thu, 5 Feb 2015 12:33:27 +0000
Message-ID: <CA+s+GJBaQJPmCBKHLPfZ-_JjarpVCnAmz8eoD=Rg2HLx_vfn=A@mail.gmail.com>
From: Wladimir <laanwj@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: text/plain; charset=UTF-8
X-Spam-Score: -1.6 (-)
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
(laanwj[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
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: 1YJLci-0004pq-P6
Subject: [Bitcoin-development] Bitcoin Core 0.10.0rc4 tagged
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: Thu, 05 Feb 2015 12:33:33 -0000
FYI, I've just tagged v0.10rc4, and pushed my signatures to the
gitian.sigs repository.
Please start your gitian builders!
Changes relative to rc3:
- 1eb14af Increase block download timeout base from 10 to 20 minutes.
- 3916a81 Increase coverage of DERSIG edge cases
- 6da2028 Add RPC test for DERSIG BIP switchover logic
- 773c30d BIP66 changeover logic
- 18695f0 Example unit tests from BIP66
- abfbeaf Change IsDERSignature to BIP66 implementation
- b6347bf Fix priority calculation in CreateTransaction
- 2448d34 Avoid storing a reference passed to SignatureChecker constructors
- 1bbad80 Use separate SignatureChecker for CMutableTransaction
- 6a02ef8 [Qt] don't allow amount changes when AmountSpinBox is read-only
- b61940b Change Coin Control first column label
- c5044bc sleep-wait on genesis block during init with -reindex
- b24ff47 Make empty byte arrays pass CheckSignatureEncoding()
- ed4206a fix crash: CoinControl "space" bug
- 58259ad qt: fix broken unicode chars on osx 10.10
- aaf55d2 186a517 Add a -rpckeepalive option to disable RPC use of
HTTP persistent connections.
Hopefully this will be the last release candidate before the 0.10 final release.
Wladimir
|
