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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <grarpamp@gmail.com>) id 1U41mi-0006I5-Ei
for bitcoin-development@lists.sourceforge.net;
Sat, 09 Feb 2013 04:11:28 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.128.178 as permitted sender)
client-ip=209.85.128.178; envelope-from=grarpamp@gmail.com;
helo=mail-ve0-f178.google.com;
Received: from mail-ve0-f178.google.com ([209.85.128.178])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1U41mh-0008GC-O4
for bitcoin-development@lists.sourceforge.net;
Sat, 09 Feb 2013 04:11:28 +0000
Received: by mail-ve0-f178.google.com with SMTP id db10so3891574veb.37
for <bitcoin-development@lists.sourceforge.net>;
Fri, 08 Feb 2013 20:11:22 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.58.214.231 with SMTP id od7mr9855301vec.44.1360383082207;
Fri, 08 Feb 2013 20:11:22 -0800 (PST)
Received: by 10.220.219.79 with HTTP; Fri, 8 Feb 2013 20:11:22 -0800 (PST)
In-Reply-To: <CABsx9T1D08uOenXch7ZwrEaCeOdFCFOtzK8ochN8z3REGm0mLQ@mail.gmail.com>
References: <CABsx9T1D08uOenXch7ZwrEaCeOdFCFOtzK8ochN8z3REGm0mLQ@mail.gmail.com>
Date: Fri, 8 Feb 2013 23:11:22 -0500
Message-ID: <CAD2Ti2_QPACgF61nPLTDrBad1ext3pKfXYF68gYctMQJQFugUA@mail.gmail.com>
From: grarpamp <grarpamp@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
(grarpamp[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: 1U41mh-0008GC-O4
Subject: Re: [Bitcoin-development] 0.8.0rc1 status
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: Sat, 09 Feb 2013 04:11:28 -0000
> Linux builds of 0.8.0rc1 are in good shape; easily gitian-reproduceable.
> Windows builds are varying with every compile, and I think I finally
> The OSX build is in pretty good shape, but needs
> So: I think the path forward is to announce 0.8.0rc1 with the binaries
> we've got, to get more testing.
With this new minor bump, I'd like to encourage the project to perform
a build check on FreeBSD 8.3 (gcc), and 9.1 (should be clang/llvm).
I'll try to get to 8.x but may not be able to in time.
|
