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
|
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 <laanwj@gmail.com>) id 1TMGN0-0003ZQ-BW
for bitcoin-development@lists.sourceforge.net;
Thu, 11 Oct 2012 10:52:02 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 74.125.82.53 as permitted sender)
client-ip=74.125.82.53; envelope-from=laanwj@gmail.com;
helo=mail-wg0-f53.google.com;
Received: from mail-wg0-f53.google.com ([74.125.82.53])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1TMGMz-0001va-CZ
for bitcoin-development@lists.sourceforge.net;
Thu, 11 Oct 2012 10:52:02 +0000
Received: by mail-wg0-f53.google.com with SMTP id dr1so1020868wgb.10
for <bitcoin-development@lists.sourceforge.net>;
Thu, 11 Oct 2012 03:51:55 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.180.90.201 with SMTP id by9mr19878863wib.5.1349952715181; Thu,
11 Oct 2012 03:51:55 -0700 (PDT)
Received: by 10.194.6.73 with HTTP; Thu, 11 Oct 2012 03:51:55 -0700 (PDT)
In-Reply-To: <CA+8xBpdLo+VoHiJNJWNn+NPHj9v33=bSXBhkBeoLr73z-qFrBQ@mail.gmail.com>
References: <CA+8xBpdLo+VoHiJNJWNn+NPHj9v33=bSXBhkBeoLr73z-qFrBQ@mail.gmail.com>
Date: Thu, 11 Oct 2012 12:51:55 +0200
Message-ID: <CA+s+GJDqsFmDhPM=NgLRehokiHBBGdfieDbYUYH4a9ETBCrPPA@mail.gmail.com>
From: Wladimir <laanwj@gmail.com>
To: Jeff Garzik <jgarzik@exmulti.com>
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: 1TMGMz-0001va-CZ
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Post-0.7.1 tree freeze for ultraprune
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, 11 Oct 2012 10:52:02 -0000
On Wed, Oct 10, 2012 at 8:40 PM, Jeff Garzik <jgarzik@exmulti.com> wrote:
> Proposal: following 0.7.1 release, freeze the tree. Do not pull
> anything, until ultraprune is pulled (or rejected, but I think the
> latter is unlikely).
Yes, I think this is a good idea. Getting ultraprune in should be a priority.
I've just pulled all the small stuff that was already ACKed for
post-0.7.1, so IMO the freeze can start.
Wladimir
|
