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-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <gmaxwell@gmail.com>) id 1VIxih-0007Zk-Le
for bitcoin-development@lists.sourceforge.net;
Mon, 09 Sep 2013 09:25:21 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.215.44 as permitted sender)
client-ip=209.85.215.44; envelope-from=gmaxwell@gmail.com;
helo=mail-la0-f44.google.com;
Received: from mail-la0-f44.google.com ([209.85.215.44])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1VIxif-0006zT-07
for bitcoin-development@lists.sourceforge.net;
Mon, 09 Sep 2013 09:25:19 +0000
Received: by mail-la0-f44.google.com with SMTP id eo20so4777394lab.3
for <bitcoin-development@lists.sourceforge.net>;
Mon, 09 Sep 2013 02:25:09 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.152.44.225 with SMTP id h1mr15885856lam.15.1378718709864;
Mon, 09 Sep 2013 02:25:09 -0700 (PDT)
Received: by 10.112.89.72 with HTTP; Mon, 9 Sep 2013 02:25:09 -0700 (PDT)
In-Reply-To: <CAAS2fgRrgrfmjSKMkDWcqnRNfS_S2pZaCECb7OiaGr3B+kMqww@mail.gmail.com>
References: <CAAS2fgRrgrfmjSKMkDWcqnRNfS_S2pZaCECb7OiaGr3B+kMqww@mail.gmail.com>
Date: Mon, 9 Sep 2013 02:25:09 -0700
Message-ID: <CAAS2fgT8_tp_4aGG_4jRAjO3ROCh9JNz1dHMfCi0qstEG8K7wA@mail.gmail.com>
From: Gregory Maxwell <gmaxwell@gmail.com>
To: Bitcoin Development <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
(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: 1VIxif-0006zT-07
Subject: Re: [Bitcoin-development] Some current turbulence on the Bitcoin
network: DB corruption errors on start from Bitcoin-qt / Bitcoind
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: Mon, 09 Sep 2013 09:25:21 -0000
On Mon, Sep 9, 2013 at 1:53 AM, Gregory Maxwell <gmaxwell@gmail.com> wrote:
> More information will be forthcoming once a patch is available.
I now have a patch up for review.
https://github.com/bitcoin/bitcoin/pull/2982
(You should wait until other developers have had a chance to review
before rushing out and applying it. The checklevel=2 workaround is
adequate for now.)
|
