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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <gmaxwell@gmail.com>) id 1YI1Kv-0007Cm-W6
for bitcoin-development@lists.sourceforge.net;
Sun, 01 Feb 2015 20:41:42 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.213.180 as permitted sender)
client-ip=209.85.213.180; envelope-from=gmaxwell@gmail.com;
helo=mail-ig0-f180.google.com;
Received: from mail-ig0-f180.google.com ([209.85.213.180])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1YI1Kv-0001nA-5w
for bitcoin-development@lists.sourceforge.net;
Sun, 01 Feb 2015 20:41:41 +0000
Received: by mail-ig0-f180.google.com with SMTP id b16so12988169igk.1
for <bitcoin-development@lists.sourceforge.net>;
Sun, 01 Feb 2015 12:41:35 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.42.25.144 with SMTP id a16mr16470401icc.66.1422823295627;
Sun, 01 Feb 2015 12:41:35 -0800 (PST)
Received: by 10.107.6.18 with HTTP; Sun, 1 Feb 2015 12:41:35 -0800 (PST)
In-Reply-To: <2472472.uuMyyaUxq1@1337h4x0r>
References: <2472472.uuMyyaUxq1@1337h4x0r>
Date: Sun, 1 Feb 2015 20:41:35 +0000
Message-ID: <CAAS2fgTz55DbLEgHXXmWX-mxjWD8k4Omp9E+xJeWkhUw6Yribw@mail.gmail.com>
From: Gregory Maxwell <gmaxwell@gmail.com>
To: xor@freenetproject.org
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
(gmaxwell[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: 1YI1Kv-0001nA-5w
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Bitcoin Core 0.9.4 not on bitcoin.org?
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: Sun, 01 Feb 2015 20:41:42 -0000
On Sun, Feb 1, 2015 at 8:08 PM, xor <xor@freenetproject.org> wrote:
> Why is that?
Because Binaries on Bitcoin.org have always been unaffected by the
issue 0.9.4 was released to address.
> Also, is it correct that there wasn't a release candidate before the release?
> Sounds dangerous to me.
The changes were tried first by many people as part of git master.
This was narrow bug fix backport required to prevent the software from
no longer working at all for people who compiled it themselves and
received software updates for their system.
|
