blob: 5a021bb2ea12e648bc25691120878c86f04a9245 (
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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <grarpamp@gmail.com>) id 1Uht0B-0007l4-22
for bitcoin-development@lists.sourceforge.net;
Thu, 30 May 2013 02:54:07 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.212.53 as permitted sender)
client-ip=209.85.212.53; envelope-from=grarpamp@gmail.com;
helo=mail-vb0-f53.google.com;
Received: from mail-vb0-f53.google.com ([209.85.212.53])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Uht0A-00043d-Et
for bitcoin-development@lists.sourceforge.net;
Thu, 30 May 2013 02:54:07 +0000
Received: by mail-vb0-f53.google.com with SMTP id p13so5522559vbe.12
for <bitcoin-development@lists.sourceforge.net>;
Wed, 29 May 2013 19:54:01 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.52.69.200 with SMTP id g8mr3136662vdu.4.1369882440913; Wed,
29 May 2013 19:54:00 -0700 (PDT)
Received: by 10.220.115.7 with HTTP; Wed, 29 May 2013 19:54:00 -0700 (PDT)
Date: Wed, 29 May 2013 22:54:00 -0400
Message-ID: <CAD2Ti2_pp3jgsq3s93NGdLi-Ojtyu11DTu9aoqy657DteqSdUg@mail.gmail.com>
From: grarpamp <grarpamp@gmail.com>
To: 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: 1Uht0A-00043d-Et
Subject: [Bitcoin-development] 0.8.2 branch
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, 30 May 2013 02:54:07 -0000
Should there not be a 0.8.2 branch laid down at 09e437b (v0.8.2)
in which the like of release build stoppers or critfixes such as d315eb0
are included... for those tracking that level of defect without
wishing to track all the growing post release slush in HEAD?
|
