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
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <gmaxwell@gmail.com>) id 1QcoQZ-0001gs-E7
for bitcoin-development@lists.sourceforge.net;
Sat, 02 Jul 2011 00:51:19 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.220.175 as permitted sender)
client-ip=209.85.220.175; envelope-from=gmaxwell@gmail.com;
helo=mail-vx0-f175.google.com;
Received: from mail-vx0-f175.google.com ([209.85.220.175])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1QcoQY-00079j-O9
for bitcoin-development@lists.sourceforge.net;
Sat, 02 Jul 2011 00:51:19 +0000
Received: by vxa37 with SMTP id 37so4118981vxa.34
for <bitcoin-development@lists.sourceforge.net>;
Fri, 01 Jul 2011 17:51:13 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.161.102 with SMTP id xr6mr1665805vdb.27.1309567873209; Fri,
01 Jul 2011 17:51:13 -0700 (PDT)
Received: by 10.52.186.167 with HTTP; Fri, 1 Jul 2011 17:51:12 -0700 (PDT)
In-Reply-To: <1309567578.2541.26.camel@Desktop666>
References: <1309478838.3689.25.camel@Desktop666>
<20110701080042.GA657@ulyssis.org>
<BANLkTim-QWvtfL65mo3uW7ESiehKOmHjtw@mail.gmail.com>
<BANLkTi=DWUhGmoHcQB5EPZHF71JE71gcTg@mail.gmail.com>
<1309524016.2541.0.camel@Desktop666>
<BANLkTimobc7471uBMLBecYT3vz0GO6RLzQ@mail.gmail.com>
<BANLkTinqcaDMci-YmYHpDd1sZ_RT9pEOvw@mail.gmail.com>
<BANLkTi=zG4o5igBFX=4Yg340B0QGF42RBQ@mail.gmail.com>
<1309567578.2541.26.camel@Desktop666>
Date: Fri, 1 Jul 2011 20:51:12 -0400
Message-ID: <BANLkTin4pUDX9EmNpPkgxg1i6MbkVME0GQ@mail.gmail.com>
From: Gregory Maxwell <gmaxwell@gmail.com>
To: Matt Corallo <bitcoin-list@bluematt.me>
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: 1QcoQY-00079j-O9
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] 0.3.24
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, 02 Jul 2011 00:51:19 -0000
On Fri, Jul 1, 2011 at 8:46 PM, Matt Corallo <bitcoin-list@bluematt.me> wrote:
> Personally, I have little preference, sipa and gmaxwell fall on the side
> of cherry-pick, but I think it might be good to do a broad-base test of
> CWallet in 0.3.24 so potential bugs can be found in it before crypto and
> 0.4. In either case, I dont think we should spend too much time as this
> is just a minor update release, just get it out the door so we can focus
> on 0.4 (hopefully) without interruption.
The fact that this will -rc before full release softens my concern some.
I did a lot of semi-automated testing of cwallet+crypto (in the
encrypted and non-encrypted states) which I really don't want to redo
for cwallet alone.
|
